DELETE Company Role

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description repeats that the action cannot be undone, adding no new behavioral insights beyond what annotations provide. It does not disclose authorization requirements, side effects, or rate limits.

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 relatively short but contains unnecessary repetition ('This cannot be undone' and 'Permanently removes' each appear twice). The inclusion of API version and endpoint details is useful but could be condensed. Overall, it is somewhat redundant but not overly 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?

For a destructive tool with no output schema, the description fails to explain what happens upon success (e.g., no return value, confirmation). It also omits any mention of potential cascading effects or dependencies, leaving the agent without sufficient context to handle the tool correctly.

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 fully describes both parameters (company_id, id) with clear descriptions. The description merely lists them as required, offering no additional semantic meaning, such as format, constraints, or relationships between 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 the action (DELETE) and the resource (Company Role) in the first sentence, but then inconsistently refers to 'Company Settings' later, which is misleading because the endpoint is specifically for roles. This ambiguity reduces clarity, though the core purpose is still discernible.

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 does not provide any guidance on when to use this tool versus alternatives like patch_company_role or post_company_role. It only states that the deletion is permanent, but lacks context about prerequisites or scenarios where deletion is appropriate.

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