update-outlook-contact

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

The tip about emailAddresses array replacement adds behavioral context beyond annotations (readOnlyHint=false, destructiveHint=true). However, it does not cover other important behaviors like side effects, permissions, or what happens to unspecified properties.

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 very concise with one main sentence and a tip. No redundant information, but could be slightly more structured with a separate 'behavior' section.

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?

No output schema, and the description lacks details on error handling, property retention, or required entity existence. For an update tool with many properties, this is insufficient.

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?

With 75% schema description coverage, the schema already describes most parameters. The description adds only the emailAddresses replacement tip, which is already implied by the schema. Minimal additional meaning.

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 verb 'update' and the resource 'contact object'. It distinguishes from sibling tools like create-outlook-contact and delete-outlook-contact, making purpose unambiguous.

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 explicit guidance on when to use this tool versus alternatives. The description only includes a tip about emailAddresses behavior, not usage context or prerequisites.

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