query_attachment

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the operational duality (one vs many) and the requirement to set payload.action, but does not reveal additional behaviors such as file overwrite handling, error responses, or rate limits. With annotation coverage, the description's additional value is modest.

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 exceptionally concise at two sentences, with the primary function first and the operation selector second. Every word earns its place; no filler.

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 query/download tool with no output schema, the description adequately conveys the two call patterns and the filesystem effect. However, it does not specify the return format for the 'many' action (e.g., an array of attachment metadata) beyond the schema's property descriptions. This is a minor gap given the schema richness, but the description alone is slightly incomplete for the listing 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?

The input schema provides 100% parameter description coverage, detailing action, attachment_id, output_file, entity_type, and entity_id. The description reinforces the action parameter usage ('Set payload.action to 'one' or 'many'') but adds no new information beyond the schema. Baseline 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 clearly identifies the tool's function: downloading a single attachment or listing all attachments for a test case/test run. The verbs 'download' and 'list' plus the resource are specific, and the second sentence explains the action discriminator, distinguishing it from sibling add_attachment tools.

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 implies usage contexts via the two action modes but provides no explicit guidance on when to choose this over the alternative sibling tools like add_attachment or get_cases. It does not state exclusions or prerequisites, so usage guidance is only partially inferable.

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