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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the meaningful detail that what is returned is the *draft* HTML and that edits flow through update_page, but says nothing about permissions or state beyond that.

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 compact sentence with the resource and its key payload front-loaded and no filler. Every clause earns its place, including the workflow pointer.

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?

An output schema exists, so return structure need not be explained, and only one parameter is involved. The description covers what is returned and the update cycle, making it essentially complete, though the draft-state concept could be elaborated slightly.

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?

There is one parameter and schema description coverage is 100%, so the schema already documents page_id. The description adds no parameter detail (no format, source, or identifier semantics), leaving the baseline 3 appropriate.

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 specifies the resource returned ('A page') and its payload ('current draft HTML'), which implicitly conveys retrieval. However, it never states an explicit verb and does not distinguish itself from adjacent siblings like get_page_guide, get_page_stats, or preview_page.

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 parenthetical 'edit this and save it with update_page' implies the workflow and routes to the update_page sibling, which is useful. But it gives no explicit when-to-use versus get_page_stats, preview_page, or list_pages, so guidance is only implied.

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