getAttachment

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

No annotations are provided, so the description must disclose behavioral traits. 'Show attachment' implies a read operation, but it does not explicitly state that it is non-destructive, nor does it mention any other behaviors like permissions or side effects. Minimal disclosure.

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?

Extremely concise (two words), but this under-specification harms clarity. Every sentence should earn its place; here, the description is too brief to be helpful.

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 tool has two parameters (with nested object) and no output schema, the description is completely inadequate. It fails to explain what 'show' returns, how format affects output, or any other necessary context.

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%, and the description adds no information about parameters. The input schema includes 'format' (enum) and 'attachmentId', but the description does not clarify their meaning or usage.

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 'Show attachment' provides a verb and resource, but is vague. It does not specify what 'show' entails (e.g., retrieve metadata, display content, or download). Among siblings like 'downloadAttachmentAsBase64Content' and 'updateAttachment', this lacks specificity to differentiate, but it is not a tautology.

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 given on when to use this tool versus alternatives like downloadAttachment... or deleteAttachment. The description provides no context for selection.

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