wafeq_simplified_invoices_download_retrieve

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

The description goes well beyond the annotations. It discloses the exact response format ('base64-encoded PDF bytes plus its size and content type'), explicitly states 'Nothing is modified,' and reveals the HTTP method (GET). This complements the readOnlyHint, idempotentHint, and destructiveHint annotations with concrete behavioral details the agent needs to understand the call's effect and output.

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 compact and front-loads the key facts in a summary line (READ-ONLY, returns a PDF, resource, endpoint). It is slightly redundant, repeating 'Download simplified invoice PDF' and 'Endpoint for downloading a PDF of the simplified invoice,' but the overall structure is clear and beats verbose alternatives.

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 one-parameter download tool, the description is complete. It tells the agent the endpoint, the resource, the required id, the response format, and that nothing is modified. Annotations cover safety traits, and the input schema covers the required parameter. No critical information is missing for correct invocation.

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 has one required `id` parameter with 0% schema description coverage, so the description must compensate. It partially does by showing the URL template `/simplified-invoices/{id}/download/`, which implies `id` is the simplified invoice identifier. However, it never explicitly defines `id` or its format, leaving the agent to infer the parameter's meaning from the endpoint rather than from a direct description.

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 operation: 'Download simplified invoice PDF' and 'Endpoint for downloading a PDF of the simplified invoice.' It identifies the specific verb (download), the resource (simplified invoice PDF), and even includes the exact endpoint path. It distinguishes itself from sibling download tools (e.g., invoices, bills, quotes) by explicitly naming 'Simplified Invoices' as the resource.

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 makes it obvious when to use this tool: when a PDF of a simplified invoice is needed. It provides clear context by labeling the resource 'Simplified Invoices' and showing the GET endpoint, which implicitly separates it from other download_retrieve siblings. However, it does not explicitly mention alternatives or state when not to use it, so it stops short of a perfect score.

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