delete_contact

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It warns about caution for deletions, implying destructive behavior, but does not detail permissions needed, reversibility, or rate limits. The description adds some context (e.g., the default behavior with '*') but lacks comprehensive behavioral traits, making it adequate but incomplete.

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 well-structured with a purpose statement, warning, and parameter/return details in bullet-like format. It is appropriately sized and front-loaded, though the warning could be integrated more seamlessly. Every sentence adds value, with minimal waste.

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 complexity (destructive operation with one parameter) and no annotations, the description does a good job covering purpose, parameters, and caution. An output schema exists, so return values need not be explained. However, it lacks details on error conditions or behavioral nuances, leaving minor 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 schema description coverage is 0%, so the description must fully compensate. It explicitly defines the 'number' parameter as a phone number or '*' to delete all contacts, with a default value of '*', adding crucial meaning beyond the bare schema. This covers the single parameter comprehensively, making it highly effective.

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 verb ('Delete') and resource ('contact or all contacts'), making the purpose specific and unambiguous. It distinguishes between deleting a single contact by phone number and deleting all contacts with the '*' wildcard, which is essential for understanding the tool's scope.

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 includes a warning to 'Use with caution, especially when deleting all contacts,' which provides clear guidance on when to be careful. However, it does not explicitly mention when to use this tool versus alternatives (e.g., other deletion tools like 'delete_file'), nor does it specify prerequisites or exclusions, leaving some contextual gaps.

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