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

Annotations already disclose readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered; the description adds the useful behavioral detail that the bio accepts a restricted HTML subset (<b>, <i>, <a>, <br>). It does not say whether omitted fields are left untouched, whether the whole record is replaced, or what permissions are needed for a page other than home.

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, front-loaded with the action and scope, and the HTML constraint follows immediately. Nothing is redundant with the title or with structured fields.

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?

All three params are optional and fully described in-schema, and no output schema exists to explain. Still, for a mutation tool the description leaves open whether a partial update preserves the other field, and it never differentiates this from rename_page, which is the most likely sibling confusion.

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% (limits, defaults, and the list_pages reference for 'page' are all documented in-schema), so the baseline is 3. The description contributes only the HTML-tag allowance for the bio field, which is a modest but real addition beyond the schema's length constraint.

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 names a specific verb ('Change') and resource ('the name and/or bio shown at the top of a page'), so the agent knows exactly which fields are mutated and where. It does not, however, distinguish itself from the sibling rename_page, which plausibly touches naming as well, so a routing ambiguity remains.

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?

Usage is implied by the phrase 'shown at the top of a page,' which conveys that this edits a page's profile display rather than page content. There is no explicit when-to-use, no when-not, and no mention of the relevant alternative (rename_page) or that 'page' defaults to home when omitted (that only lives in the schema).

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