delete_module

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

The description merely repeats the action 'delete' without elaborating on consequences (e.g., cascading deletions, reversibility, or permission requirements). Annotations already indicate destructiveHint=true, but the description adds minimal value beyond that. It also incorrectly includes 'workspace_slug' in the args, which is not present in the input schema, creating confusion.

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 short but contains unnecessary 'Args:' formatting and an extraneous parameter. It could be more concise by directly stating the required parameters without the label.

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 is destructive (destructiveHint=true) and has no output schema, the description should explain what happens on success/failure, any dependencies, and the role of the missing workspace_slug. It fails to provide this context, making it incomplete for an agent.

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?

Schema coverage is 0%, so the description must compensate. It attempts to describe parameters but incorrectly includes 'workspace_slug', an argument not in the schema. While it correctly mentions 'project_id' and 'module_id' as UUIDs, the extra erroneous parameter misleads the agent.

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 'Delete a module by ID', using a specific verb ('delete') and resource ('module'). This distinguishes it from sibling tools like create_module, retrieve_module, and update_module.

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 on when to use this tool versus alternatives. It does not specify any preconditions, dependencies, or cases where deletion might be inappropriate (e.g., if the module has associated work items).

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