query

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

No annotations exist. Description only mentions 'read-only' and param placeholders. Lacks details on query limits, error handling, or result format, which are critical for a query tool.

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 is concise but omits important guidance. Front-loads 'read-only', but the brevity sacrifices necessary detail.

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 simple query tool with no annotations or output schema, the description is insufficient. It does not cover return behavior, pagination, or error scenarios, leaving agents underinformed.

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?

No schema description coverage. Description adds only param placeholder usage ('?') but does not explain sql syntax requirements or params type/format, leaving significant ambiguity.

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?

Clearly states 'read-only SELECT query' with optional params, distinguishing it from sibling tools like mutate (for writes) and table description tools.

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?

Implicitly suggests use for read queries via 'read-only', and '? placeholders' hints at parameterization. No explicit when-not or alternatives provided, but sibling context fills some gaps.

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