save_attachment

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

With no annotations, the description carries the full burden of disclosing behavior, but it only restates the basic download-and-save action. It does not mention whether an existing file is overwritten, whether directories are created, what happens if the attachment is missing, or what the operation returns.

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 efficient sentence with the action front-loaded and no filler. It is appropriately compact, though it is lean enough that other dimensions have to compensate for missing context.

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 file-writing tool with no annotations and no output schema, the description is too thin to be complete. It omits return behavior, filesystem side-effect details, and any relation to sibling tools, so an agent lacks important context for correct invocation.

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% and each parameter already has a meaningful description, so the baseline is 3. The description adds no new parameter-level detail beyond echoing the existence of a file path, which keeps it at that baseline.

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 a specific action (download an email attachment) and an output destination (save to a file path), so an agent can broadly understand what the tool does. It does not explicitly distinguish this from the sibling download_attachment, leaving some ambiguity about which tool to choose.

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 gives no guidance on when to prefer save_attachment over download_attachment, list_attachments, or other email tools, and it states no prerequisites or exclusions. The only usage signal is the verb phrase itself, which is not enough for routing among highly similar siblings.

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