wafeq_bills_download_retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety bar is partially met by structured data. The description adds genuine value beyond this by disclosing the return format ('base64-encoded PDF bytes plus its size and content type') and reaffirming 'Nothing is modified.' This tells the agent exactly what to expect in the response and that the call is side-effect-free.

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-loaded with the most important signals (READ-ONLY, returns a PDF, Bills, endpoint). However, there is redundancy: 'Download bill PDF' and 'Endpoint for downloading a PDF of the bill' convey nearly identical information, and the READ-ONLY prefix duplicates the annotation. It could be tightened without losing meaning.

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 single-parameter tool, the description is essentially complete: it covers purpose, endpoint, return shape (base64 PDF bytes, size, content type), and side-effect guarantees, with annotations covering safety and idempotency. Minor omissions are error conditions (e.g., bill not found) and how to source a valid `id`, but neither is critical at this complexity level.

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 description coverage is 0%, so the description must compensate. The endpoint template 'GET /bills/{id}/download/' implies that `id` is the bill's identifier used in the URL path, which adds meaning beyond the bare string schema. However, it doesn't state where to obtain the id (e.g., from wafeq_bills_list) or any format/validity constraints, leaving partial but not full compensation for the coverage gap.

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 a specific verb and resource: 'Download bill PDF' and 'Endpoint for downloading a PDF of the bill.' The header line ('Bills · GET /bills/{id}/download/') and the 'Bills' label clearly differentiate this from the many sibling *_download_retrieve tools (invoices, payslips, quotes, etc.), so an agent can tell them apart without opening schemas.

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?

Usage context is implied but not explicit. The 'Bills' prefix and the endpoint /bills/{id}/download/ signal that this tool is for downloading bill PDFs, and the READ-ONLY marker plus 'Nothing is modified' imply a safe retrieval operation. However, the description never explicitly states when to use this over alternatives like wafeq_bills_retrieve or names the sibling download tools it should be preferred to.

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