delete-contact-folder

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

Annotations already indicate destructiveHint=true. The description adds valuable behavioral details: the default folder cannot be deleted (returns error), and the folder typically moves to Deleted Items rather than being permanently removed. No contradiction with 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 relatively short and includes a tip, but some repetition (e.g., 'Delete contactFolder' and 'Deletes a contact folder'). Still efficient and frontloaded.

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 no output schema, the description adequately explains the outcome (deletion, non-permanent, error for default) and provides a necessary prerequisite (get folder ID). It is complete for a single-purpose delete tool.

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 100%, so baseline is 3. The description does not add specific parameter meaning beyond what the schema provides; it only mentions getting the folder ID via list-contact-folders, which is not about parameter semantics.

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) and the specific resource (contact folder other than default). It distinguishes from sibling delete tools by specifying the folder type and the limitation on the default 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 clear context: when to use (to delete a non-default contact folder), when not to (default folder cannot be deleted), and a practical tip to get the folder ID via list-contact-folders. It doesn't explicitly exclude other delete tools but the resource specificity is sufficient.

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