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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds what is being mutated (name, slug, visibility), but does not disclose the consequences of a destructive mutation, e.g. that changing the slug breaks previously shared links or that visibility changes who can access an existing page.

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?

A single front-loaded sentence that names the actions in the order of the schema fields, with zero filler or repetition. Nothing needs trimming.

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?

With an output schema present, return values need not be explained, and annotations cover the destructive/write nature. The description accounts for all three mutable attributes, leaving only permission requirements and partial-update behavior unstated.

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%, and the schema supplies format constraints (slug 3-40 lowercase letters/digits/hyphens) and enum meanings (private invitation-only vs public link). The description merely restates the same three fields, so the baseline 3 applies with no added semantics such as whether the update is partial or atomic.

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 pairs a specific verb (rename/change/switch) with a specific resource (page) and enumerates the three mutable attributes: name, slug, visibility. That is enough to distinguish it from the read-oriented siblings (get_page, list_pages) and the publish siblings, though it never names an alternative explicitly.

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?

There is no when-to-use or when-not-to-use guidance. An agent is not told whether this requires ownership/admin rights, whether publish_page is the right call instead when the page does not yet exist, or what to do for a partial vs. full update.

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