custom_menus_delete_custom_menu

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

Annotations already include destructiveHint=true, so the destructive nature is known. The description adds the token-level requirement, which is not in annotations and is useful. It does not elaborate on irreversibility or side effects, but with the destructive hint and idempotent hint present, the added value is minimal but relevant. 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?

The description is a single sentence, front-loads the action, then adds the essential token requirement. There is no redundant wording or filler. Perfectly concise.

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 single-parameter destructive tool with no output schema, the description covers the core purpose and a key authentication detail. It does not mention permanence or cascading effects, but the destructiveHint annotation already signals that. The token requirement is the missing piece that the description supplies, making it sufficiently complete for an agent to invoke 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?

The input schema provides a description for customMenuId: 'ID of the custom menu to delete', which is clear and complete. The tool description does not add extra semantics beyond that. Since schema coverage is 100%, a baseline of 3 is appropriate.

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 states the action explicitly: 'Delete Custom Menu Link'. It clearly identifies the resource and the operation, and it is distinguishable from sibling tools like custom_menus_create_custom_menu or custom_menus_update_custom_menu. No ambiguity.

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 provides a critical usage prerequisite: 'requires an agency-level token, not a location PIT'. This helps the agent know when it can be used. However, it does not mention when to prefer deletion over update or other alternatives, nor does it describe any conditions for deletion eligibility. It gives a necessary constraint but lacks comparative guidance.

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