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

With no annotations, the description carries the full burden, and it discloses the critical non-obvious behavior: items are REPLACED wholesale with the full new tree, and omitting them preserves the existing ones. It omits permission/auth requirements and error behavior, but the destructive replace semantics are made explicit.

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?

Three tight sentences, each earning its place, with the high-impact REPLACE behavior front-loaded before the workflow and prerequisite. No redundant restatement of the title or name.

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 mutation tool with a rich nested schema and an existing output schema, the description supplies the essential workflow and replace semantics an agent needs to call it correctly. Return values needn't be described since an output schema exists.

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 100%, so the schema already documents name, items, and menuId, including the 'omit to keep' and 4-level nesting notes. The description reinforces the replace semantics but adds no new parameter syntax or format detail, so the baseline of 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 and resource ('Rename a menu and/or REPLACE its items') and pins down the exact semantics of the mutation (full-tree replacement). This clearly separates it from create-menu, delete-menu, and list-menus among the siblings.

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 an explicit workflow: read the current tree with list-menus, edit, send the whole tree, plus a prerequisite rule (read get-skill-doc site-assets-contract before the first call). The alternative (list-menus) is named and the condition that selects each step is stated.

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