Menus: reorder

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the bar is lower; the description still adds real value by spelling out the partial-list semantics (unnamed menus follow in their current order) and advising confirmation before running. It does not contradict the destructive hint.

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?

Four short sentences, each carrying a distinct point (action, partial-list behavior, sibling routing, confirmation warning), with the core action front-loaded. There is mild redundancy between the description's ordering sentence and the schema's parameter description.

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 tool with an output schema absent but annotations present, the description covers semantics, side effects, and alternative-tool routing. Only minor items such as the response shape or failure modes are unaddressed, which is acceptable here.

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 100% and the single parameter already documents the comma-separated format and the example '92,90,91'. The description restates the same ordering behavior, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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+resource ('Set the order of menus') and immediately disambiguates from the sibling menus_update by scoping that tool to role changes. An agent can distinguish this from menus_reorder_items, menus_update_item, and menus_update without opening a schema.

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?

Gives the rationale for why ordering matters (a role is shown only its first menu) and names the alternative tool (`menus_update`) for the adjacent task of changing a menu's role. It stops short of stating when reordering is unnecessary, but the routing condition to the sibling is explicit.

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