Query Next Session Page

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

No annotations provided, so description must carry behavioral info. It correctly indicates read-only nature and that limits are respected. However, it omits details like session lifecycle, error handling on invalid session, or pagination behavior.

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?

Single sentence, front-loaded with purpose and key constraint. No wasted words.

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?

For a pagination tool with no output schema and no annotations, the description is too minimal. It lacks prerequisites (session must exist from ob_start_query_session), side effects (advances session cursor), and details on pagination limits. Incomplete for safe autonomous usage.

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 0% with no parameter descriptions. The description does not explain any parameter beyond the implied sessionId. No additional meaning is provided for orderBy, pageSize, or profile.

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 it runs the next page for a read-only query session, and the title reinforces 'Query Next Session Page'. It implies distinction from ob_query_page and ob_query_prev_page but does not explicitly differentiate.

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?

No guidance on when to use this tool versus siblings like ob_query_page, ob_query_prev_page, or ob_start_query_session. The description only states a limitation (no bypassing limits) without usage context.

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