add-mail-attachment

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

Description discloses the 3MB limit constraint, which is not in annotations. No contradiction with annotations (readOnlyHint=false, destructiveHint=true). Consistent with create operation.

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?

Single sentence plus a succinct tip. Every element is valuable and front-loaded.

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?

Covers max size and format but omits return value description. Given no output schema, the return format (e.g., attachment ID) would be useful. Adequate for simple operation.

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 tip provides essential JSON format for the body parameter, adding meaning beyond the schema which lacks explicit structure for file attachments.

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?

Description clearly states it creates a new attachment and specifies the types. It distinguishes from sibling 'create-mail-attachment-upload-session' by implication, but does not explicitly differentiate.

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?

Lacks guidance on when to use this tool vs. alternatives like the upload session. No description of prerequisites or exclusions.

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