mailosaur_files_get_attachment

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

Description mentions 'Returns base64 content' but omits key aspects like authentication needs, size limits, error conditions, or whether the tool is read-only. With no annotations, the burden is high, and this is insufficient.

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?

Two short sentences, front-loaded with the purpose. Efficient, though the output format detail is minor. No unnecessary words.

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?

Despite the simplicity (one required param, no nested objects), the description lacks parameter semantics, behavioral traits, and output schema information. Incomplete for reliable usage.

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 single parameter 'attachmentId' has no description in the schema (0% coverage), and the tool description does not explain it. No guidance on how to obtain the ID or what values are valid.

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 action ('Download') and the resource ('a message attachment'), which distinguishes it from sibling tools like mailosaur_files_get_email and mailosaur_files_get_preview.

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 on when to use this tool instead of alternatives. No prerequisites or context provided, leaving the agent to infer usage from the purpose alone.

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