get_voucher

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

No annotations provided, but the description does not disclose any behavioral traits such as idempotency, required permissions, error conditions, or response structure. Minimal disclosure beyond the basic action.

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?

Single sentence with no extraneous words. Front-loaded with verb and object. Every word earns its place.

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?

Tool is simple (one parameter, no output schema). Description is adequate for basic usage but lacks information about return values, pagination, or error handling. Could be more complete with minimal effort.

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% (only one parameter), and the description adds no additional meaning beyond the schema's own description ('The ID of the voucher to retrieve'). Baseline score applies.

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 uses a specific verb ('Get') and resource ('voucher by ID') with source ('sevdesk'). It clearly distinguishes from sibling tools like list_vouchers (list all) and book_voucher (mutation).

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 explicit guidance on when to use this tool vs alternatives. Implied by purpose (need a specific voucher), but no when-not or references to siblings like get_voucher_positions.

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