Delete A Crew

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description reinforces this by stating 'cannot be undone' and 'permanently removes', which adds emphasis but no new behavioral insights. No additional context about associated data or authorization is provided.

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 concise but contains some redundancy (e.g., 'This cannot be undone' repeated). It front-loads the core purpose and includes the API details, which is useful. Minor repetition prevents a perfect score.

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 well-defined parameters, the description covers the essential behavior. However, it lacks mention of the return value or success response, and does not explain the meaning of 'Directory records' fully. Given the absence of an output schema, this is an acceptable but not thorough completeness.

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 has 100% coverage with descriptions for all six parameters. The description only reiterates that project_id and id are required, offering no added semantic meaning beyond what the schema already provides. Baseline score of 3 applies.

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 is 'Deleting a Crew associated with the specified Project' and emphasizes permanent deletion. This verb+resource combination is specific and distinguishes the tool from sibling delete tools for other resources. The inclusion of the API endpoint also adds clarity.

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 lacks guidance on when to use this tool versus alternatives. It only states what the tool does without providing context such as when not to use it, prerequisites, or references to other deletion methods. Given the large set of sibling tools, this omission is significant.

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