update-email

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

Explicitly states idempotency (aligned with idempotentHint annotation), explains batch uses Graph $batch for efficiency, and notes it doesn't modify content. Adds value beyond annotations.

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 efficient paragraph front-loading the core purpose. Every sentence provides essential detail without redundancy. Well-structured from general to specific.

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 all key aspects: actions, parameters, batch vs single, safety, and return behavior ('status confirmation per message'). No gaps given the tool's complexity and lack of output schema.

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?

Despite 100% schema coverage, the description adds meaning by explaining how parameters relate to actions (e.g., dueDateTime only for flag) and the id vs ids usage. Enhances understanding significantly.

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?

Clearly states 'Update message state without modifying content', specifying verb (update), resource (message state), and scope (state only). Distinguishes from siblings like read-email, send-email which handle content.

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?

Describes each action and its parameter requirements (e.g., mark-read uses id; flag accepts id or ids). Provides context for batch vs single. No explicit exclusions, but the differentiation from siblings is implied.

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