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

Annotations already declare destructiveHint=true, and the description reinforces it with '(irreversible)' while adding genuinely new behavior: the cascade to menu items and the fallback semantics for a block bound to the menu. That side-effect disclosure goes beyond the annotation, though permissions/authorization requirements are still unstated.

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?

Front-loads the action and its irreversibility, then the cascade/fallback consequence, then the confirmation rule and prerequisite. Efficient and ordered by importance, though the trailing 'Rules:' fragment is terse and slightly abrupt.

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 destructive single-parameter tool with an output schema already covering return values, the description supplies everything else an agent needs: reversibility, cascade behavior, binding fallback, user-confirmation trigger, and a required pre-read. Nothing material is missing.

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 coverage is 100% and the single parameter's own description ('Menu id from list-menus') already tells the agent where the value comes from; the prose adds no syntax, format, or constraint beyond it. Baseline 3 is appropriate when the schema fully carries the parameter.

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?

States a specific verb and resource ('Delete a navigation menu') plus the cascade scope ('and its items'), which distinguishes it cleanly from update-menu, create-menu, and the other delete-* siblings. An agent knows exactly what this tool targets without opening the schema.

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?

Gives real conditional guidance ('Confirm with the user when it is in use') and a prerequisite workflow step (read the site-assets-contract skill doc before the first call). It stops short of naming alternatives such as update-menu for non-destructive edits, so it is clear context without explicit exclusions.

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