create_attachment

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

Without annotations, the description only says 'create' and 'upload'—it does not disclose potential side effects, required permissions, data size limits, or error behavior. No mention of authentication requirements or reversibility.

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?

Description is extremely concise and front-loaded with the action, but it is minimal to the point of under-specification. However, it efficiently communicates the primary purpose without wasted 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?

For a simple create tool with full schema coverage, the description is adequate but lacks any statement about return values or post-creation behavior. No output schema exists, so the description could have briefly noted what the response contains.

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 covers all parameters with 100% description coverage; description adds no additional parameter semantics beyond what schema already provides.

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 tool creates a new attachment and explicitly mentions upload, which distinguishes it from sibling tools like update_attachment, get_attachment, and list_attachments.

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. Does not mention prerequisites, exclusions, or when to use assign_attachment or other related tools. The usage is implied from the create verb but not explicit.

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