delete_menu

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

No annotations are present, so the description carries the full burden. It merely says 'Delete a navigation menu' without disclosing that deletion is irreversible, whether special permissions are needed, or if cascading effects (e.g., removing menu items) occur. For a destructive action, this lacks critical context.

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, 'Delete a navigation menu', which is concise and front-loaded with the action. Every word is necessary, and there is no redundant information.

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's simplicity (one required parameter, no output schema), the description and schema cover the basic action. However, it omits important contextual warnings such as irreversibility, permission requirements, or whether deleting a menu can fail if it is in use. This leaves the agent without guidance on edge cases.

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 input schema provides 100% coverage with the property 'id' described as 'Menu ID to delete'. The tool description adds no additional semantic meaning beyond what the schema already documents, so the baseline score of 3 applies.

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 uses the specific verb 'Delete' plus the resource 'navigation menu', which clearly distinguishes it from sibling menu tools like create_menu, update_menu, and get_menu. No ambiguity about what action is performed.

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 is provided on when to use this tool vs alternatives, nor any prerequisites such as checking if the menu is in use or confirming its existence. The presence of many sibling menu tools makes this omission noticeable.

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