update-email

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

Description discloses the mutation nature (update email state) and idempotent actions, consistent with annotations. It adds detail beyond annotations by listing specific actions and their effects. No contradictions.

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?

Three sentences, front-loaded with the core purpose. Each sentence adds necessary detail without redundancy. Highly concise and well-structured.

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?

Description covers inputs and actions but omits return value or error conditions. For an update tool, the agent may need to know what the response looks like. Missing output schema increases the need for description completeness.

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 100%, but the description adds value by linking parameters to specific actions (e.g., dueDateTime only for flag). This organizational context helps the agent understand parameter usage.

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 updates email state and lists specific actions like mark-read, flag, unflag, etc. This distinguishes it from sibling tools like read-email or manage-category.

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 explains actions and parameters but lacks explicit guidance on when to use this tool versus alternatives, such as apply-category or manage-focused-inbox. No when-not-to-use or exclusion criteria.

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