get_page_summary

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

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions 'plaintext summary' and 'fast', but lacks details on return format (e.g., size limits), error conditions, authentication needs, or any side effects. Significant gaps remain.

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 extremely concise—two short sentences—with no wasted words. It front-loads the key purpose and is efficient for an agent to parse.

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 tool's simplicity (one required parameter, no nesting) and presence of an output schema, the description is minimally adequate. However, it could be improved by noting that the output is plaintext only and that the tool is ideal for quick summaries, but the current level is sufficient for a basic understanding.

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 description adds no meaning to the single 'title' parameter beyond what the schema shows. With 0% schema description coverage, the description should clarify expected format, case sensitivity, or valid values, but it does not.

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 tool returns a 'lead-section plaintext summary' of a page, which differentiates it from sibling tools like 'get_page' (full page) and 'get_page_sections' (all sections). The verb 'get' is implied, and the resource is explicitly identified.

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 'Fast context anchor' implies quick retrieval, but there is no explicit guidance on when to use this tool versus siblings, nor any when-not-to conditions. Usage context is implied rather than stated.

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