deleteMenuItem

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

Discloses permanence, no undo via API, no soft delete, and records not recoverable. Also specifies the return format. Annotations already provide destructiveHint=true and readOnlyHint=false, and the description adds crucial context beyond them. No contradiction.

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?

Well-structured with sections and bold key points. Every sentence adds value, front-loads the essential action, and avoids fluff.

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 purpose, usage context, behavior, and return value. Warns about bulk use. Could mention potential cascading effects on references, but for a simple deletion it is fairly complete.

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 one required integer parameter with 0% description coverage. Description explicitly states 'Required: menu_item_id' and confirms it identifies the record by ID. Adds some meaning but no format, constraints, or examples.

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 it deletes a menu item permanently by ID. It distinguishes from sibling updateMenuItem (modify without removing) and deleteMenu (deletes a menu), making the specific verb+resource+scope unambiguous.

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 single menu entry' and provides a 'See also' reference to updateMenuItem. Warns about destructive nature and to confirm intent before bulk use. Lacks explicit alternatives for bulk or multiple items, but context is clear.

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