contactDelete

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It states deletion and the not-in-use condition, implying a destructive and conditional operation, but it does not mention irreversibility, what happens if the contact is in use, or any authorization requirements.

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 a single front-loaded sentence that states the action and the key precondition, with an API reference link appended. Every word contributes meaning.

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 single-parameter tool, the description is mostly complete: it identifies the action, the resource, and a precondition. However, with no annotations or output schema, it does not explain failure behavior when the contact is in use or confirm the permanence of deletion.

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 already documents contact_id with 100% coverage, and the description's 'contact profile' aligns with the parameter meaning. The description adds no extra format, source, or validation guidance, but the schema is sufficient on its own.

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 uses a specific verb, 'Delete', with a clear resource, 'a contact profile', and adds a distinguishing constraint, 'that is not in use'. This clearly separates it from sibling tools like contactUpdate or contactAdd.

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 phrase 'that is not in use' provides clear context for when deletion is allowed. However, it does not explicitly name alternatives such as contactUpdate for modifying an in-use profile or contactDomainAssociate for reassigning it.

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