teamleader_delete_company

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

The destructiveHint=true annotation already flags the operation as destructive, but the description adds meaningful context with 'This is irreversible,' informing the agent that the deletion cannot be undone. This goes beyond the generic annotation and is a critical behavioral fact for invocation decisions.

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 exactly two short sentences with no filler. The core action is front-loaded, and the essential caveat (irreversibility) follows immediately, ensuring every word contributes value.

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 delete operation, the description conveys the action and the most important consequence. It does not mention potential restrictions (e.g., whether a company with linked records can be deleted), but given the simple profile, the destructive annotation, and the absence of an output schema, the essentials are adequately covered.

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 only parameter ('The company ID to delete') with 100% schema description coverage, so the description does not need to add parameter details. The tool description offers no additional parameter semantics, which is appropriate given the schema's completeness.

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') plus a resource ('a company') and platform ('Teamleader Focus'), making the operation unambiguous. The additional warning 'This is irreversible' reinforces the purpose and distinguishes it from non-destructive company tools like create, update, get, and list.

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 clearly implies when to use the tool—whenever a company must be deleted—and the resource name distinguishes it from sibling delete operations on other entities. However, it gives no explicit when-not-to-use guidance or caveats about alternatives, such as whether soft-delete or archiving should be preferred in certain situations.

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