Rename page

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

Annotations already declare openWorldHint=false and destructiveHint=false, so the agent knows this touches only local diagram state and is non-destructive; the description is consistent with that. It adds the effect (new_name becomes the visible tab label), but says nothing about failure behavior when no page matches or whether the change is persisted/undoable.

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 short sentences, front-loaded with purpose, then the identification constraint, then the effect. Every sentence carries information and there is no filler.

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 simple, single-target mutation with no output schema and fully documented parameters, the description covers purpose, target selection, and outcome. It omits only edge cases (page not found, rename of the active tab), which are minor at this complexity.

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 schema details precedence rules, so baseline is 3. The description contributes genuine semantics the schema does not encode: the schema only marks new_name as required, while the description supplies the anyOf-style constraint that at least one page identifier must be given.

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 an existing page (tab)") and clarifies the domain meaning of "page" as an editor tab. It is self-evidently distinct from add_page/delete_page/list_pages, but it never names or contrasts an alternative sibling, so it stops short of full differentiation.

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 sentence "At least one of page_id / page_name / page_index is required" gives a real precondition for invocation, which is useful. However, there is no guidance on when to prefer this over add_page/delete_page or how to resolve a missing page, leaving usage largely implied.

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