quiz bu lëkkale ak tegtal · Diggante Niveau
Jumtukaayi jëmmal ngir LLM Agents Quiz
Dafay saytu ni tur yi ak seeni tegtal di doxalee ci tànneefi model yi, lu tax ay schema yu tar ak njuumte yuñ mëna jëfandikoo dañu am solo, ak lu tax jumtukaay yu bari di gaañ ndawu liggéey yi.
Laaj 1 de 8
What does the model actually use to decide how to call a tool?
Xoolaatal laaj bu nekk8 laaj
Sooy def quiz bi, tontu yi ak leeral yi dañuy feeñ.
- What does the model actually use to decide how to call a tool?
- The tool's source code
- The name, description, schema and returned text
- The server's latency history
- The programming language the tool is written in
- Why might an agent use prefixes such as github_create_issue and jira_create_issue?
- Prefixes make tools run faster
- APIs require prefixes
- They keep similar tools from different services apart
- They reduce the size of JSON Schema files
- Which parameter design is most likely to produce correct arguments?
- An enum listing the allowed values
- A free-text string called 'value'
- An untyped field with no description
- A parameter named 'x'
- What makes a good tool error message?
- A numeric error code only
- A generic 'something went wrong'
- Nothing, so no tokens are spent
- It explains what went wrong and suggests what to try next
- Why can adding many tools reduce agent performance?
- Models can only call one tool per conversation
- Each definition takes up context, and overlapping tools make selection harder
- Tools stop working once there are more than five
- Tool count has no effect
- Compared with mirroring every API endpoint one-to-one, what does the guide recommend?
- Fewer, higher-level tools shaped around real tasks
- Exposing every endpoint so the agent has full coverage
- Using only one tool for everything
- Letting the model write its own HTTP requests
- Why should a tool paginate or truncate its output by default?
- To hide data from users
- Because models cannot read numbers
- To avoid filling the context window with low-value data
- Because JSON Schema requires it
- Why make tools idempotent or give them an idempotency key?
- It makes descriptions shorter
- It lets the model skip schemas
- It speeds up model inference
- A retried call will not create duplicate records