Prepare Read-only Query

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

The description explicitly states that the tool does not execute the target query, which is a key behavioral trait. However, with no annotations provided, the description should also disclose other aspects like side effects, permissions, or limits. It does not, relying only on the read-only and safety preview hints.

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 of 18 words, which is concise and front-loaded with the main verb. However, given the complexity of the tool (8 parameters, no schema descriptions), the description could benefit from a bit more structure, such as listing the key parameters or outputs.

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 8 parameters, no output schema, and no annotations. The description only provides a high-level overview. It lacks information on return values, parameter semantics, and usage context. For an agent to correctly invoke this tool, more detail is needed.

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%, meaning none of the 8 parameters have descriptions in the input schema. The description itself does not explain any parameter purpose or constraints. This is a significant gap, as the agent has no information about what each parameter controls.

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 prepares candidate tables, fields, read-only SQL drafts, and safety previews without executing the query. The verb 'prepare' is specific and the resource is well-defined. However, it does not explicitly differentiate from sibling tools like ob_generate_query or ob_build_select, which may have overlapping functionality.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical use cases, or situations where it should be avoided. This leaves the agent without context for selection.

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