delete-contact-folder

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

Beyond the annotations (destructiveHint=true), the description adds important behavioral traits: the default folder cannot be deleted, and the folder typically lands in Deleted Items rather than being permanently removed. This provides valuable context beyond what annotations offer.

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 with one sentence and a structured tip. It is front-loaded with the purpose and then provides additional guidance, with no redundant information.

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 covers purpose, usage constraints, and post-deletion behavior. It could mention the response format (e.g., success indication) since there is no output schema, but overall it is fairly complete for a delete operation.

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 100%, so each parameter is adequately described in the schema. The description does not add significant extra meaning to the parameters beyond what is already present in the schema, thus scoring baseline 3.

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 (delete a contact folder) and specifies the resource (contactFolder other than default). It distinguishes from sibling tools by emphasizing the non-default folder constraint.

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 explicitly tells when to use (delete a non-default contact folder) and when not (default folder causes error). It also provides a tip on how to obtain the folder ID via list-contact-folders, giving clear alternatives and context.

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