get_page

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

No annotations are provided, so the description itself must carry behavioral information. It discloses that the page is cached, implying possible staleness, and public, implying no auth requirement. 'Fetch' also indicates a read operation; cache-miss behavior is not covered but is secondary for a single-page fetch.

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 sentence front-loads the action and resource, and the parenthetical gives a working example without redundancy. There is no filler or restatement of the schema.

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 one required parameter and an output schema present, the description covers input semantics, cache/public behavior, and single-page scope sufficiently. It lacks only explicit routing guidance versus siblings and cache-miss specifics, both minor.

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?

The schema provides only the parameter name path_or_url with no description, so the description fully compensates by specifying accepted forms: a relative path like '/about-yongbo-yu' or an absolute HTTPS URL. This is exactly the semantic detail the schema lacks.

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 verb 'Fetch' plus resource 'cached public page' and the qualifier 'one' make the tool's scope explicit. The path and absolute HTTPS URL examples disambiguate it from list_site_pages and search_site, which operate over collections.

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 phrase 'one cached public page by path or absolute HTTPS URL' tells an agent this is the right tool when a specific page identifier is already known. It does not explicitly name sibling alternatives like list_site_pages or search_site, so the decision is left to inference rather than spelled out.

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