save_email_attachment

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

With no annotations provided, the description carries full burden. It states it saves to disk and returns a confirmation message, but does not disclose side effects (e.g., whether the email is modified, marked as read, or deleted). The description is acceptable but could be more transparent about behavioral traits.

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 brief and well-structured: a one-line purpose, then a clear arg list, then return value. It is front-loaded and contains no unnecessary filler. However, the return value line could be omitted if the output schema is present, but it is fine overall.

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 4 required parameters, no annotations, and an output schema (context indicates it exists), the description covers the basics adequately. However, it lacks edge-case behavior (e.g., multiple emails matching subject keyword, attachment not found, overwriting files). It is minimally complete but could be more thorough.

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 coverage is 0%, meaning the schema has no descriptions. The description provides explicit meaning for each parameter in the docstring (e.g., 'account: Account name (e.g., "Gmail", "Work", "Personal")'), which adds significant value beyond the structured schema.

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: 'Save a specific attachment from an email to disk.' It uses a specific verb and resource, and the sibling tool list includes other email attachment tools like 'list_email_attachments', so it distinguishes well.

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. It does not mention prerequisites (e.g., email must be fetched first) or when not to use it. The context of sibling tools is not leveraged to provide usage distinctions.

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