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

With no annotations provided, the description carries the full behavioral disclosure. It makes clear this is a no-cost read operation, returns real saved markup rather than working memory state, resolves partial templates, and produces exactly the representation the preview would serve.

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?

The description is focused and front-loaded: the opening sentence names the tool's real behavior, and each subsequent part adds concrete value. There is no repetition of schema information and no filler.

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 simple two-parameter read operation with an output schema and no annotations, this description is complete. It covers what the agent gets, how it differs from the most similar sibling, and an important cost consideration. An agent can choose and invoke the tool correctly.

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 no schema-level parameter documentation and the description does not explicitly define project_guid, page, or how to obtain the project identifier. The term 'one page' and the page string schema give some guidance, but the required project_guid is left to inference.

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+resource: it reads one page's actually saved markup, with partials resolved, matching the preview output. This clearly distinguishes it from get_project_context and other sibling tools that return summaries or mutate 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 says when to use it: verify what actually survived a save. It also contrasts get_project_context, which returns a summary that intentionally omits most attributes, and notes that reading is free and does not spend the user's quota.

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