Get all attachments

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

Annotations already carry the safety profile (readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds the administration scoping context beyond the annotations but does not disclose additional traits such as pagination, response shape, or what counts as an attachment. There is no contradiction with the 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 short and front-loaded, with only three brief lines. However, the opening 'Get all attachments.' repeats the title verbatim and adds no value, while the '[Attachments] GET /attachments' line provides marginal API-path detail. Minor redundancy prevents a 5.

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 tool with one optional enum parameter, no required inputs, no output schema, and rich safety annotations, the description covers the essential invocation facts: it lists all document attachments for the administration. The main gap is not clarifying whether returned attachments span all invoice/document types or how they relate to the sibling attachment tools, but this is minor for a list operation.

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 100%; the single 'administration' parameter is already fully documented in the input schema with its enum and purpose. The description adds no new parameter-level semantics beyond echoing the administration scope, so the baseline of 3 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 states a specific verb and resource: 'Get a list of all available document attachments for this administration.' The scope clarifies it lists all attachments rather than invoice-specific ones, which implicitly distinguishes it from sibling tools like upload/download/delete_sales_invoice_attachment. However, it does not explicitly name any sibling to differentiate against, so it falls short of a 5.

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 provided on when to use this tool versus alternatives such as upload_sales_invoice_attachment, download_sales_invoice_attachment, or delete_sales_invoice_attachment. The scope statement 'for this administration' gives some context, but there are no explicit conditions, exclusions, or alternative routing to help an agent decide.

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