Delete Module

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

Annotations already convey destrutiveness (destructiveHint: true) and non-read-only behavior (readOnlyHint: false). The description adds 'permanently' reinforcing irreversibility, but it does not detail side effects, permission requirements, or what happens to associated data. With annotations covering the core safety profile, this is adequate but not enhanced.

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, front-loaded with the action and object, with no superfluous words. It is concise and efficient.

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 deletion tool with one parameter and rich annotations, the description is mostly complete. It correctly identifies the action and target. However, it does not mention how to discover the module key or what happens on missing keys, which could be useful context, but the idempotentHint suggests repeated calls are safe.

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 schema describes the lone parameter 'key' as 'Module key' with 100% coverage, so the description adds little beyond that. The phrase 'by key' simply restates the schema's parameter meaning without additional context like format or how to obtain the key.

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 tool's function: 'Permanently delete a sidebar module by key.' It uses a specific verb ('delete') and resource ('sidebar module'), distinguishing it from sibling tools like create_module, update_module, and get_modules.

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 implies usage when a sidebar module needs to be removed, but it does not explicitly state when to use it versus alternatives or mention prerequisites (e.g., obtaining the key via get_modules). No exclusions or alternative tool references are provided.

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