delete_emergency_contact

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

With no annotations, the description must disclose behavior, but it only states it's a 'mutation' and shows variables. It does not mention permanence, side effects, permissions, or what happens to the contact, leaving the agent without critical behavioral context.

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 extremely concise, with a single compact line that identifies the category, mutation name, and variables. Every token earns its place, making it highly scannable and efficient.

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?

For a simple delete operation with no output schema and no annotations, the description should at least explicitly state the action and any consequences. It fails to do so, relying entirely on the mutation name and schema, leaving the agent without necessary context for invocation.

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 input schema provides 100% coverage for both parameters, including descriptions for 'id' and 'customer_slug'. The description adds an example variable format, but this is redundant with the schema, so the baseline of 3 applies.

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 mutation name 'deleteEmergencyContact' clearly indicates the tool deletes an emergency contact, and the inclusion of 'Emergency Contacts' provides context. It is distinct from sibling tools like 'create_emergency_contact' and 'update_emergency_contact', though the description lacks an explicit natural-language statement of the action.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or context for deletion. The description only lists variables and an example, omitting any situational advice.

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