get_driving_license

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does disclose a key behavioral trait: the user will be prompted for consent before data is returned. This is meaningful context, though it does not cover other behaviors like error handling or the document_id requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, and every sentence carries essential information (what it does and the consent behavior). No redundancy or wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is moderately complex with three parameters and no output schema. The description covers the consent behavior but omits practical details like the document_id requirement for multiple stored licences (present only in the schema) and what happens if consent is denied. The schema helps, but the description alone is not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description's mention of 'specific fields' aligns with the fields parameter but adds no new semantics beyond the schema, which already describes the fields and purpose parameters clearly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves specific fields from a stored driving licence, using a specific verb and resource. It distinguishes itself from sibling tools like get_passport and get_national_id by naming the driving licence specifically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving driving licence fields but provides no explicit guidance on when to use this tool versus alternatives like get_document or when not to use it. The consent note gives context but no comparative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.