Menu Link Delete

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

With no annotations provided, the description carries the full burden and discloses almost nothing beyond the mutation implied by "delete." It does not state whether deletion is permanent, whether child links are orphaned, or whether the link is removed from the menu tree entirely.

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?

One short sentence with no waste, which is appropriate for a trivial delete. However, the extreme brevity is under-specification rather than disciplined conciseness, since important behavior is simply omitted.

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 tool with no annotations and no parameter documentation, the description omits the irreversibility warning and the source of link_id. The presence of an output schema excuses it from explaining return values, but the deletion semantics remain unexplained.

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 0% and the single parameter link_id is undocumented in both schema and description. The description adds no meaning about where the ID comes from or its format, so an agent has no guidance on supplying it correctly.

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?

"Delete a menu link" gives a specific verb and resource, so an agent knows exactly what operation is performed. It does not, however, distinguish this from siblings like menu_link_update, menu_link_create, or paragraphs_item_delete beyond the obvious verb difference.

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 delete versus update or unlink a menu link, no prerequisite (e.g., obtaining link_id from menu_link_list), and no warning about irreversibility. The agent must infer all usage context from the name alone.

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