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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether deletion is permanent, whether deleting a section also removes its submenu items, or what permissions are required — meaningful gaps 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?

Two short sentences, action first, the disambiguating identifier rule second. No filler and nothing to trim.

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 output schema and half its parameters undocumented, the description covers the single biggest invocation ambiguity (which id to pass). It still lacks cascade/permanence behavior and identifier mutual-exclusivity, which an agent needs before calling a delete.

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 only 50% (item_id and section_id are undocumented), and the description fills exactly that gap by explaining which identifier targets a top-level item versus a submenu item. It still leaves open whether both may be passed simultaneously or what happens if neither is supplied.

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 portal menu item) with the domain object precisely named, so it is distinguishable from update_portal_menu_item and list_portal_menu_items. It omits an explicit sibling comparison, keeping it just below a 5.

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 clause 'section_id for a top-level item, item_id for a submenu item' tells the agent which identifier to pick, which is real usage guidance. However, there is no statement of when to use this versus update/delete_portal_page, no note that exactly one identifier should be supplied, and no mention that the action is irreversible.

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