delete_a_secondary_contact

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'DESTRUCTIVE' and 'deletes data' are redundant but consistent. Adds 'Confirm with the user before calling' as a behavioral guideline not in 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 repetitive, stating 'Delete a secondary contact' three times. It includes a header with emoji and HTTP method, which adds some structure but is not optimally concise.

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 deletion tool, the description covers purpose and a confirmation guideline. It lacks details on idempotency (though annotation says true), cascade effects, or response, but is minimally adequate.

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 any additional context about the 'id' parameter beyond the schema's description of 'Secondary Contact's id'.

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 explicitly states 'Delete a secondary contact' multiple times, clearly identifying the verb and resource. It distinguishes from sibling delete tools like delete_a_contact by specifying 'secondary contact'.

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?

Provides a clear instruction to confirm with the user before calling, which is a usage guideline. However, it does not specify when to use this tool versus alternatives such as delete_a_contact for primary contacts or other delete tools.

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