Delete a menu item

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the destructive nature is covered. The description adds valuable behavior beyond annotations: it discloses that children are re-parented to the top level rather than deleted. This is a non-obvious side effect that agents need to know. 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?

Two concise sentences, no filler. The core action is front-loaded, and the critical child-re-parenting behavior is stated immediately after. Every word earns its place.

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 simple 2-parameter tool with annotations covering the safety profile and full schema descriptions, the description is complete. It covers the key non-obvious behavior (child re-parenting) and needs no explanation of return values since there is no output schema. An agent has everything necessary to call it correctly.

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 description coverage is 100%, with both 'id' and 'site_id' having descriptions in the schema. The tool description adds no additional parameter-specific semantics beyond what the schema provides. According to the rubric, with high schema coverage, the baseline is 3, and no extra value is added here.

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 the verb 'Remove' and the resource 'one item from a navigation menu', distinguishing it from broader tools like delete_menu (which removes an entire menu). It also adds a unique behavioral detail (re-parenting of children) that further clarifies what the tool does. This is specific and not a restatement of the name.

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?

The description gives clear context for when to use this tool (to delete a single menu item) but does not explicitly mention alternatives or when-not-to-use cases. However, the behavioral note about children being re-parented instead of deleted helps an agent decide if this is the right operation, especially compared to deleting the whole menu. There are no exclusions or alternative tools named, though the context is clear enough.

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