Remove a company agreement

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

The description confirms a destructive action, which matches the destructiveHint=true annotation. However, it does not disclose any additional behavioral traits such as whether the deletion cascades to related licenses or requires specific permissions, leaving gaps that annotations don't cover.

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, which is concise but omits necessary details about parameters and usage. It earns its place but should be slightly expanded without being verbose.

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 no output schema and a destructive action, the description should provide more context about consequences or prerequisites. Currently, it is too minimal to fully inform an agent's decision.

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?

With 0% schema description coverage, the description carries the full burden but fails to explain any of the three required parameters (id, company, project). It only mentions 'by id' but does not specify the roles of other parameters.

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 it deletes a contract/license from a company by id. It uses a specific verb ('Delete') and resource ('contract/license'), and distinguishes from sibling tools like add_company_agreement and update_company_agreement.

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 provides no guidance on when to use this tool versus alternatives (e.g., deactivating via update_company_agreement). It implies usage for removal but lacks explicit context or exclusions.

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