Get Page Context

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

No annotations provided, so description carries full burden. It discloses return values (page, tags, limited related context, provenance) and error handling (if slug missing, search for correct slug first). However, it does not explicitly state the tool is read-only or mention any side effects. This is a minor gap, hence 4.

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?

Highly concise and well-structured with headings, bullet points, and clear separation of sections. Each sentence is informative without redundancy.

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?

Given the presence of an output schema and the tool's moderate complexity, the description covers usage, error handling, parameter context, and return values adequately. It also differentiates from siblings, making it complete for agent decision-making.

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 100% with good parameter descriptions. The description adds minimal extra meaning beyond the schema; it mentions 'limit' implicitly via 'maximum related items' but the schema already says that. Baseline 3 is 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 clearly states the purpose: 'Read a page plus nearby memory context.' It uses a specific verb ('Read') and resource ('page'), and distinguishes from siblings like `put_page` (write) and `query`/`search` (broad recall).

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?

Explicit when-to-use: 'after finding a slug and needing page, tags, links, backlinks, timeline, or chunks in one call.' Also when-not-to-use: 'broad recall without a slug; use `query` or `search` first.' Clearly guides agent decision.

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