get_page

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

No annotations exist, so the description carries the full burden. It does disclose the return payload (markdown body plus title and source URL), which is useful given there is no output schema, but it says nothing about truncation, missing/invalid page IDs, permission scope, or whether 'full' is actually full.

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 clause with the most important information (full markdown content) front-loaded and no filler. It borders on under-specification rather than verbosity.

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 two undocumented parameters and no output schema, the description should at minimum explain how to obtain the IDs and what the response looks like. It partially covers the return shape but leaves the input contract entirely implicit.

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 0% — both site_id and page_id are bare strings with no descriptions. The description mentions only 'one page' and adds nothing about ID formats, how site_id scopes the lookup, or whether IDs come from search/list_sites results.

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?

Names the resource precisely (one page) and the payload (full markdown body, title, source URL), which distinguishes it from bulk siblings like search and list_sites. It lacks an explicit verb ("get"/"retrieve") and never names an alternative, but the scope is unambiguous.

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?

No indication of when to use this versus search, neighbors, or render_site, and no preconditions stated. The agent must infer from the name alone that this is the single-page fetch after an ID is known.

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