create-outlook-contact

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

The description says 'Add a contact', which is a non-destructive action, but the annotation destructiveHint: true indicates it is destructive. This is a contradiction. Annotations already indicate it's a mutation (readOnlyHint: false), but the description adds no additional behavioral context beyond stating the action.

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 short (one sentence), which is concise but lacks necessary detail. It is front-loaded with the action but omits important context.

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?

Given the complex nested schema, lack of output schema, and minimal annotations, the description is incomplete. It does not explain return values, error cases, or clarify the ambiguous 'contacts endpoint of another contact 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 coverage is 67%, so some properties have descriptions. The description does not explain that the 'body' parameter is the contact object or its structure. It adds minimal value beyond the schema.

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 it adds a contact to the root Contacts folder or to another folder, which is clear but vague. It does not differentiate from the sibling tool 'create-contact-in-folder', which likely has similar functionality.

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 provided on when to use this tool versus 'create-contact-in-folder'. There are no prerequisites or context about requiring a folder ID.

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