delete_contact_property

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 states the action and HTTP method, implying mutation, but it does not disclose whether the deletion is permanent, what happens to contacts using the property, or any permission requirements. For a destructive operation, this is a significant gap.

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 sentence that includes the essential action and HTTP endpoint, with no wasted words. It is front-loaded and earns its place.

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 one parameter, the description is adequate but incomplete. It does not mention irreversibility, return value, or error behavior. Given that there is no output schema and no annotations, a note about permanence or effects on dependent data would make it more complete.

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 provides a 100% description coverage for the single 'id' parameter ('The contact property id.'). The description adds no additional meaning beyond what the schema already states, so the baseline score of 3 is appropriate.

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 action (delete) and resource (contact property), and includes the HTTP method and path (DELETE /contact-properties/:id), making it unambiguous. It is easily distinguished from sibling tools like get_contact_property or update_contact_property.

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 implies a destructive action through the verb 'delete' and the HTTP DELETE method, but it does not explicitly state when to use it vs. alternatives, nor does it mention any prerequisites or consequences (e.g., irreversibility). It is clear enough for a simple delete operation but lacks explicit guidance.

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