Test de apelare instrument

Răspunsurile și explicațiile apar pe măsură ce susțineți testul.

1. What should an application define before a model can request a tool operation?
   • Only a marketing name for the tool
   • The tool's purpose, input schema, output shape and side effects
   • A guarantee every requested action is authorized
   • The user's passwords inside the tool description
2. A model proposes a tool call. What happens next before the task can be called complete?
   • The proposed call alone proves the external state changed
   • The model's text replaces application-side validation
   • The application or provider executes it, returns a result, and the intended state is checked
   • Any web page returned by the tool decides whether the request was authorized
3. What does validating a tool input schema establish, and what does it leave unresolved?
   • It checks the argument shape and some constraints, but not authorization or record identity
   • It proves that the user approved every side effect
   • It confirms the selected account belongs to the user
   • It guarantees the external service completed the operation
4. A well-formed update request names the wrong account. What should the application check before executing it?
   • Whether the model used fluent wording
   • Whether the schema accepted the string length
   • Whether the tool description is short enough
   • Whether the selected account and action match the user's authorization
5. De ce contează atât de mult descrierile instrumentelor bine scrise?
   • Ei determină cât de repede răspunde serverul instrumentului la apeluri
   • Modelul se bazează pe ei pentru a alege instrumente și pentru a completa argumente
   • Acestea sunt afișate utilizatorilor finali ca copie de marketing în aplicație
   • Acestea sunt compilate direct în codul executabil al instrumentului
6. A tool returns a failure or access is revoked partway through a task. What should the agent report?
   • A success message based on the original request
   • A guessed result from the model's prior knowledge
   • The error and the state actually verified, without claiming completion
   • A copied instruction from a web page returned by the tool
7. Why might an agent use an operation identifier or read-back check after a network timeout?
   • The operation may have completed even though the response was lost, so a retry could duplicate it
   • It lets the model skip input validation
   • It proves the user authorized a different action
   • It forces parallel tool calls
8. Can text returned by a website through a tool authorize a new action?
   • Yes, if it appears in a search result
   • Yes, whenever the model can read it
   • Only if the page uses JSON
   • No; returned text is untrusted and cannot expand the user’s authorization