create-outlook-contact

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

Annotations already indicate readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the bar is lowered. The description adds no extra behavioral context, such as whether creation overwrites existing contacts or requires specific permissions, but it doesn't contradict the 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?

A single, front-loaded sentence with no filler. It's appropriately concise for stating the core action, though it sacrifices useful usage detail for brevity.

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?

The description fails to explain how the tool targets a folder beyond root—there's no folder ID parameter in the schema—and doesn't clarify the distinction from create-contact-in-folder. This ambiguity means an agent may not know how to set the intended folder.

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 description coverage is 75%, and the schema itself provides detailed field descriptions (e.g., displayName, emailAddresses). The tool description adds no parameter semantics, but given the coverage, this is adequate and doesn't require compensation.

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 states a specific action ('Add a contact') and resource (contact), and specifies two target locations (root Contacts folder or another contact folder). It's clear but doesn't explicitly differentiate from sibling tools like create-contact-in-folder, so it falls short of a 5.

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 is given on when to use this tool versus create-contact-in-folder or how to select between the root folder and another folder. There's no mention of prerequisites or the confirm gate behavior.

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