Start Query Session

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

Describes the context as 'in-memory read-only,' indicating safety and temporary nature. However, lacks details on session lifecycle, memory limits, or interaction with other session tools (e.g., ob_close_query_session).

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?

A single sentence of 10 words is very concise. However, it could include more parameter guidance without losing efficiency.

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?

With 11 undocumented parameters, no output schema, and no annotations, the description is grossly insufficient for correctly invoking the tool.

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% and the description provides no explanation for any of the 11 parameters (e.g., sql, page, table, params, schema, columns, orderBy, profile, pageSize, warnings, businessTerm).

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 creates an in-memory read-only query context for follow-up paging, refinement, and summarization. This distinguishes it from direct query tools like ob_query which execute immediately.

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?

Implied usage for paging, refinement, and summarization, but no explicit when-to-use or when-not-use, nor alternatives like ob_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.