delete-menu

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

No annotations are provided, so the description must convey behavioral aspects like permanence, side effects, or permissions. The one-line description does not disclose whether deletion is irreversible, cascades to related entities, or requires special authorization, leaving significant ambiguity for a destructive operation.

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 extremely concise, using a single sentence with no filler or redundancy. While it is well-structured and front-loaded, it is arguably too brief to be fully self-sufficient, but as a structural matter it wastes no words.

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 is a destructive delete operation with no annotations, no output schema, and a sparse parameter schema, the description is incomplete. It omits crucial details such as irreversibility, effects on related menus, and any required permissions, making it insufficient for an agent to use safely.

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 schema lists a single required parameter 'menu_id' with no description (0% schema coverage). The description fails to compensate by explaining what this ID refers to, how to obtain it, or any format expectations, so the agent must rely solely on the parameter name for inference.

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 action ('Delete') and the resource ('a UI menu'), which is specific enough to understand the tool's basic function. It is not explicitly differentiated from sibling tools beyond the name, but the verb+resource combination distinguishes it from create/update/get menu operations.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of when deletion might be inappropriate. The description provides no contextual direction for an agent deciding to invoke it.

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