delete_company_contact

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

With no annotations provided, the description must disclose behavioral traits. It simply states 'Delete a company contact' without mentioning what happens on deletion (permanence, cascading effects, permissions required), or whether the operation is idempotent. This is a significant gap for a destructive operation.

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 concise phrase with no unnecessary words. It is front-loaded with the action and resource, making it easy to parse. It earns its place by clearly stating the tool's core purpose without verbosity.

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 has only one parameter and no output schema, the description is extremely thin. It lacks critical context about the consequences of deletion, any required permissions, or conditions under which deletion is allowed. The absence of annotations makes this incomplete compared to expectations for a delete operation.

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 fully documents the single parameter 'companyContactId' with its type and description, so the schema coverage is 100%. The description adds no extra meaning beyond the schema, which meets the baseline of 3.

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 'Delete a company contact' uses a specific verb ('Delete') and resource ('company contact'), clearly distinguishing it from sibling operations like create_company_contact, update_company_contact, and get_company_contact. It is immediately obvious what this tool does.

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 about when to use this tool versus alternatives, nor are there any prerequisites, exclusions, or contextual hints. For example, it does not mention that deleting a company contact is irreversible or should only be done when the contact is no longer associated with any orders.

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