save_attachment

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

No annotations are provided, so the description must fully disclose behavior. It fails to mention the destination path on disk, naming conventions, overwrite behavior, or any side effects. Additionally, with zero parameters, the tool relies on implicit context (likely the last read email), but this is not stated.

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 a single, concise sentence that communicates the core action efficiently. However, the brevity sacrifices necessary detail for a function with no parameters.

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 zero parameters and no output schema or annotations, the description should provide more context about how the tool determines which attachment, where it saves to, and any constraints. The current description is insufficient for an AI agent to use correctly without additional clues.

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 zero properties (100% schema coverage). With no parameters, the description should clarify how the attachment is identified (e.g., from context). It does not, leaving an implicit dependency unexplained. Baseline for no parameters is 4, but the lack of explanation reduces the score.

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 it saves an attachment from an email to disk. The verb 'saves' and resource 'attachment from an email' make the action unambiguous. Among many email-related siblings, this tool is distinct in that it handles attachments. However, it doesn't specify which attachment is targeted (e.g., from the most recently read email).

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 versus alternatives, nor any prerequisites (e.g., needing to have read an email first). There is no mention of conditions under which this tool should or should not be used.

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