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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate those. It adds behavioral context by indicating that this tool is only useful when there are more matches, implying pagination without saying it. This extra context complements the annotations.

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 a single sentence that is concise and front-loaded with the key condition. It has zero filler and earns its place by specifying the trigger condition.

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?

The tool has an output schema (not shown but signaled), so return values are covered. Given the simple function and annotations, the description is complete for a pagination tool. It lacks explicit mention of pagination semantics like offset/length, but the schema handles those, so it is adequate.

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%, so all parameters are documented in the schema. The description does not add any new parameter-level details beyond what the schema provides, but it does clarify the role of sessionId as coming from start_search. This is marginally helpful but not substantial, hence a baseline 3.

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 that this tool retrieves additional search results from a search initiated by start_search, distinguishing it from start_search, stop_search, list_searches, and list_sessions. It uses a specific verb-resource pair and explicitly references the starting tool.

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?

It tells agents when to use this tool (when a search still has more matches), but does not explicitly mention when not to use it or alternative tools. However, the sibling list includes start_search and stop_search, and the description implicitly differentiates it via the 'started with start_search' condition.

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