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

Annotations already declare readOnlyHint=false and destructiveHint=true, but the description adds substantial context beyond that: rev-based optimistic concurrency (a conflicting save is refused with the reason and nothing is overwritten), which operations do and do not change the rev, edit-permission rules for discussions, and the title-only fallback for image/long-body pages.

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?

Purpose is front-loaded in the first sentence, and each subsequent clause carries a distinct constraint (concurrency, edit permissions, fallbacks, required role). It is dense but nearly every sentence earns its place, with only minor packing of multiple rules into single sentences.

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 destructive mutation with no output schema, the description covers the essential edge cases an agent needs: concurrency semantics, permission requirements, read-only/archived behavior, and content-replacement limits. Nothing critical for correct invocation appears to be missing.

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 75%, with rev, pageId, and content already documented in the schema. The description adds the meaningful semantic that content replaces the whole body and explains the rev conflict behavior, but largely reinforces schema-supplied meaning, so it sits at the baseline-plus level.

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 ('Changes') and resource ('a page's title and/or body') with the key scoping detail that the body is replaced wholesale. An agent can distinguish this from siblings like set_page_archived, set_page_pinned, or update_task without opening any 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?

Provides strong context for when the tool works and when it fails: needs the editor role, archived pages are read-only, discussions are editable only by author and project owner, and images/long bodies restrict edits to the title. It doesn't name an alternative sibling for those blocked cases, so it falls just short of explicit routing.

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