delete_contact

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

Annotations already mark destructiveHint=true. The description adds a warning and a permission guideline, providing context beyond annotations. It explains what the tool does (delete) and the need for user approval.

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 concise sentences: warning, action, prerequisite. No unnecessary words. Information is front-loaded.

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 simplicity (one param, no nested objects), the description covers purpose, usage, and behavior. Output schema exists, so return values are handled. No gaps.

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 schem has one required param 'uuid' with string type, no description. The description mentions 'by its ID' but doesn't explicitly map to the uuid parameter. However, the param name is self-explanatory, so the description adds minimal value. Baseline 3 due to schema having 0% coverage, but single param clarity keeps it adequate.

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 'Deletes a contact by its ID.' The verb (delete) and resource (contact) are explicit. It distinguishes from siblings like update_contact or list_contacts by specifying the action is deletion.

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 advises 'Use list_contacts first to find the contact ID,' providing a clear prerequisite. It also instructs to ask user permission due to destructive nature. It does not explicitly state when not to use, but the warning implies caution.

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