rca_guide_delete

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

Annotations already provide destructiveHint=true. Description adds 'Permanently delete' and 'requires confirm=true', clarifying destructiveness and approval step. Does not elaborate on side effects beyond deletion.

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?

Brief two-part description with emoji. Efficient but omits token parameter, which is a structural flaw. Otherwise well-organized.

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?

Covers action, role, confirm requirement, and return format. However, missing required token parameter and no output schema provided despite context claiming one exists. Gaps reduce 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?

Schema has 0% description coverage per context; description lists only 'guide_id, confirm' but omits required 'token' parameter. Does not explain optional 'client_id' or add meaning beyond what minimal schema descriptions exist.

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?

Description clearly states 'Permanently delete one of your own equipment guides' with specific verb and resource. Distinguishes from sibling tools like rca_guide_get, rca_guide_list, etc., as none are delete operations.

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?

Explicitly mentions admin role requirement and that 'confirm=true' is needed. Provides clear context for when to use but does not specify when not to use or offer alternatives.

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