create-contact-child-folder

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, matching the create operation. The description adds minimal behavioral context: that returned contactFolder ids are mailbox-unique regardless of nesting. No further traits are disclosed beyond 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?

The description is concise: three sentences covering purpose, tip, and return value. It is front-loaded and every sentence adds value. No unnecessary 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?

The description is fairly complete given the lack of output schema and presence of annotations. It explains the purpose, usage tip, and return value. However, it does not mention error scenarios or the effect of omitting body fields beyond displayName, but for a simple creation tool, it is adequate.

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 schema coverage is 75%, and the description adds value by providing a concrete example of the body: '{ displayName: 'Sub-folder name' }'. This clarifies the minimal required field, though the schema includes many other fields. The description does not explain other parameters like contactFolderId beyond the tip.

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 purpose: 'Create a new contactFolder as a child of a specified folder.' It also mentions creating under the default folder, and the tip reinforces that this creates a sub-folder. This distinguishes it from sibling 'create-contact-folder' which likely creates a top-level folder.

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 a usage tip: 'Use list-contact-folders to discover the parent id.' It also explains the returned folder's id usability. However, it does not explicitly state when not to use this tool (e.g., for top-level folders, use create-contact-folder) or provide alternatives, but the context is clear.

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