create-contact-folder

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

The description aligns with annotations (destructiveHint: true) by indicating it creates a new folder. It adds context on where the folder is created and what it returns (the created folder with id). Though it could mention error cases, the combination with annotations provides sufficient transparency.

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?

Three sentences, front-loaded with purpose, followed by a tip and alternative. No wasted words.

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 input schema with nested objects and the lack of output schema, the description sufficiently covers the core functionality, location, and return. Minor omissions like error handling are acceptable.

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 adds value beyond the schema by providing an example: 'Body: { displayName: "Family" }', clarifying the required body parameter. With 67% schema coverage, the description compensates by highlighting the essential parameter.

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 'Create a new contactFolder under the user's default contacts folder' and mentions creating under a specified folder. It distinguishes itself from the sibling tool 'create-contact-child-folder' by explicitly naming it for sub-folders.

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: 'To create a sub-folder under an existing folder, use create-contact-child-folder.' It also gives a tip with an example of the body parameter, helping agents understand when to use this tool.

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