get_supplier_invoice

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

No annotations are provided, leaving the description to carry the burden. It only restates that the tool gets details, with no mention of read-only behavior, required permissions, response format, or side effects. The description adds little beyond the tool name's implication.

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?

The description is a single short sentence that directly conveys the purpose without unnecessary words. It is front-loaded and appropriately sized for a simple getter.

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?

For a simple getter with no output schema, the description is incomplete. It doesn't explain what details are returned, what the response looks like, or when this tool is appropriate. The absence of usage and behavioral information leaves the agent guessing.

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?

The schema defines 'id' as required number with 0% description coverage. The description does not clarify that this is the supplier invoice ID or provide any additional meaning. The parameter's purpose is inferred solely from the tool name, which is insufficient support.

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 states 'Obtenir les détails d'une facture fournisseur' (get supplier invoice details), clearly identifying the action and resource. However, it doesn't distinguish from related tools like get_invoice or list_supplier_invoices, lacking specific scope or uniqueness.

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?

No guidance is given on when to use this tool versus alternatives. The description provides no context for selecting this tool over other invoice or getter tools, and no exclusions are mentioned.

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