search_within_page

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety and idempotence are clear. The description adds behavioral context ('after global search') that clarifies the tool's position in the workflow. No negatives are omitted, and no contradiction exists.

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 two short sentences. The first sentence front-loads the core purpose, the second adds the key usage guideline. No redundancy or 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?

Despite concise purpose and guidelines, the description lacks detail about required behavior (e.g., what happens if path is invalid), parameter constraints (limit max 4, offset max 500), and relationship to siblings like 'list_headings' or 'read_section'. An output schema exists but the description does not leverage it to set expectations.

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 description coverage is 0%, so the description must compensate. It does not explain any of the four parameters (path, query, limit, offset). The agent gets no additional meaning beyond parameter names and types, which is insufficient for correct usage.

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 'Narrow within a known page after global search' uses a specific verb ('narrow') and clearly identifies the resource ('page'). It distinguishes this tool from the sibling 'search_docs' (global search) by framing it as a follow-up refinement.

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 'Prefer this over another global search' provides explicit guidance: after a global search, use this to narrow within a known page instead of re-running a broad search. It does not name the alternative sibling but implies it (likely 'search_docs'). Missing explicit when-not-to-use or prerequisite conditions.

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