Run Paged Read-Only Query

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

With no annotations, the description carries full burden. It explicitly states 'strictly read-only' and mentions pagination, but lacks details on permissions, rate limits, error handling, or behavior for invalid queries. The transparency is adequate but not thorough.

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 single sentence is front-loaded with key attributes (read-only, pagination) and is concise. However, it could include brief parameter descriptions without losing conciseness.

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 six parameters and no output schema or annotations, the description is incomplete. It does not explain required pagination behavior (e.g., need for orderBy), return format, or error responses. The agent lacks sufficient context for reliable invocation.

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%, yet the description adds no parameter-specific information. It does not explain the purpose of 'sql', 'pageSize', 'orderBy', etc., beyond what the schema names imply. The agent must guess parameter roles, risking incorrect 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 clearly states the tool runs a read-only SELECT/WITH query with server-side pagination. It specifies the verb 'Run', the resource 'query', and key features (read-only and pagination), distinguishing it from siblings like ob_query which likely lacks pagination.

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 vs alternatives like ob_query or ob_query_preview. The description does not mention prerequisites, when not to use, or alternative tools for different scenarios, leaving the agent to infer usage context.

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