Build SELECT

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

No annotations are provided, so the description carries the burden. It mentions 'read-only' and 'without executing', indicating safety, but does not disclose what happens on validation failure or whether it checks existence of table/columns.

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, concise sentence with no unnecessary words. It efficiently communicates the core purpose.

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 no annotations or output schema and 8 parameters, the description is too sparse. It does not explain what the tool returns (e.g., a SQL string) or how to use the result, and it lacks details on validation semantics.

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% and the description only enumerates parameter categories (table, columns, filters, ordering, pagination) without adding semantic details for the 8 parameters. Parameter names are self-explanatory, but no extra value is provided.

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 builds a parameterized read-only SELECT query from validated components without executing it. It specifies the verb 'Build' and the resource 'SELECT', and distinguishes from execution tools like ob_query.

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 description implies usage for constructing a query for review or further processing by noting 'without executing it', but lacks explicit guidance on when to choose this over siblings like ob_generate_query or ob_prepare_query.

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