deleteMenu

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

Beyond annotations (destructiveHint=true), the description adds: permanent deletion, cannot be undone, child items become orphaned, no soft-delete available. Discloses return format. No contradiction with annotations.

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?

Concise, well-structured. Uses bullet points and clear sections. Each sentence adds value without redundancy. Approximately 5 sentences covering all necessary aspects.

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?

Complete for a simple delete tool. Covers purpose, usage, side effects (orphaned children), prerequisites (delete children first), return value, and alternative. With no output schema, the description adequately specifies the response format.

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?

Description states 'Required: menu_id.' While the schema already defines it as required integer, the description clarifies its necessity. Could briefly explain what menu_id is, but context of tool name makes it clear. Schema coverage is 0%, so description compensates partially.

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?

Clearly states 'Delete a menu - Permanently delete a menu record by ID.' Uses specific verb and resource. Distinguishes from sibling tools by mentioning 'updateMenu' as alternative.

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 says 'Use when: removing a menu container.' Provides exclusions: child items become orphaned, delete them first. Also warns about destructive nature and suggests confirming with user. Refers to alternative tool 'updateMenu'.

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