create-contact-in-folder

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, establishing this as a write operation. The description adds context about the body format (example fields) but does not disclose additional behavioral traits beyond what annotations provide, such as effect on existing data or auth requirements.

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 efficient, with a clear first sentence and a helpful tip block. The tip is valuable but could be integrated more succinctly. Overall, every sentence serves a purpose without being verbose.

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 tool's complexity (nested body parameter, four parameters, no output schema), the description covers the key aspects: purpose, body format, and folder identification. It reasonably complements the structured schema for an agent to invoke correctly.

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?

The description summarizes the body parameter as a 'contact resource' with example fields (e.g., 'givenName, surname, displayName'), adding meaning beyond the extensive but generic schema definitions. However, not all parameters are covered, and the schema already has 75% description coverage.

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 action ('Add a contact') and the resource ('to the root Contacts folder or to the contacts endpoint of another contact folder'). It distinguishes from the sibling 'create-outlook-contact' by specifying the folder context, which is a specific verb+resource+scope combination.

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 provides explicit guidance on when to use this tool: 'Creates a contact inside a specific folder (instead of the default Contacts folder)'. It directly compares with 'create-outlook-contact' and advises to get the folder id via 'list-contact-folders', offering clear contextual alternatives.

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