search.next_text

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not indicate whether this is a read-only operation, whether it advances a search cursor, what happens when no more matches exist, or any other side effects. The phrase 'next' implies statefulness, but that is not elaborated.

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 short phrase, which is concise, but it is under-specified rather than appropriately concise. It omits critical information about parameters, state, and usage, so the brevity is a drawback rather than a strength.

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 has 3 required params, no output schema, and no annotations, the description is completely insufficient. It does not explain the return format, the meaning of 'start', the session requirement, or how this fits into the search workflow, making it nearly impossible for an agent to use correctly.

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% (no parameter descriptions), and the tool description does not explain any of the three parameters (session_id, start, query). The description adds no semantic meaning beyond what the parameter names alone suggest.

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 'Find next text match' states a clear action (find) on a resource (text match), but it is vague about what constitutes 'text' and how this differs from siblings like search.all_text or binary.search_text. The word 'next' is already in the name, so it adds little beyond the tool name.

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?

There is no guidance on when to use this tool versus alternatives. It does not explain that it is a continuation of a prior search, nor does it mention any prerequisites or exclusions. The one-line description offers no context for selection.

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