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

Annotations already mark readOnlyHint true and destructiveHint false, and the description adds meaningful behavioral context: update_page replaces content wholesale, version/sha can be passed as ifVersion/ifSha to avoid overwriting unseen changes, and expired pages remain readable and republish on the same URL. This goes well beyond the annotations.

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 sentences with no filler: the primary read action comes first, the critical update_page caveat follows, and the expired-page note finishes. Every sentence earns its place and the structure is skimmable.

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?

The tool is simple with one required slug parameter, has an output schema, and carries read-only annotations, so the description only needed to add write-safety and concurrency behavior, which it does thoroughly. Nothing an agent needs to call it correctly is 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 description coverage is 0% and the description never mentions slug, its format, or how it identifies the page. The tool name and schema imply slug is a page identifier, but the description does not add meaning beyond the schema to compensate for the low coverage.

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?

Description opens with the exact action and resource: 'Read back the CURRENT Markdown or HTML of one of your pages.' It also frames itself against update_page and clarifies it returns content plus version/sha, distinguishing it from siblings like get_page or list_my_pages.

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?

It explicitly states when to use: 'Call this before update_page whenever you did not write the live content yourself in this same conversation.' It also explains why, and notes expired pages are readable and can be republished, giving clear context for when this read tool is appropriate.

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