aruba_get_sent_invoice_zip_by_filename

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds 'Sensitive Base64 ZIP read', which warns about sensitive data being read and the output format (Base64). This provides useful context beyond annotations.

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 extremely concise: one line stating the endpoint and a brief note. It is front-loaded with the most essential information. However, it could be slightly improved by adding a brief explanation of parameters without becoming verbose.

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?

Given the number of similar sibling tools, the missing parameter guidance, and the sensitive nature of the operation (Base64 ZIP), the description lacks completeness. It does not explain when to use confirm_read, what the ZIP contains, or any prerequisite conditions. An agent would have to guess or rely on external knowledge.

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 input schema has two parameters (filename, confirm_read) but the description provides no explanation of their meaning or usage. Schema description coverage is 0%. The agent must infer parameter semantics from names alone. For a required string parameter like filename, guidance on the expected format is missing.

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 HTTP method (GET), endpoint path, and that it retrieves a sent invoice ZIP. It specifies 'Sensitive Base64 ZIP read', which adds valuable context. This clearly distinguishes it from sibling tools like aruba_get_received_invoice_zip_by_filename.

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?

There is no explicit guidance on when to use this tool vs. alternatives. The sibling tools indicate many related invoice retrieval functions (by filename, by ID, received vs. sent), but the description does not differentiate usage scenarios. Usage is implied by the endpoint name and tool name.

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