query

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states that the tool executes a SELECT query and returns rows, which communicates the core read-only behavior. It does not mention limits or edge cases, but the SELECT restriction makes the primary safety profile clear.

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, focused sentence with every word contributing meaning. It is front-loaded with the action and resource, and the return behavior is stated clearly without redundancy.

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 SELECT query tool, the description is nearly complete. The schema covers parameters fully and an output schema exists to describe return values. The only meaningful gap is the lack of guidance about when to prefer 'query' over sibling tools, but the SELECT qualifier mitigates this.

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 100%, so the baseline is 3. The description adds only the word 'parameterized', which is already captured in the schema's sql parameter description. It does not provide additional semantic value beyond what the schema already documents.

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 specific verb-resource pairing: 'Execute a parameterized SELECT query and return rows.' The SELECT qualifier distinguishes it from general execution tools like 'execute', though it does not explicitly name sibling 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?

No guidance is given about when to use this tool versus alternatives like 'execute' or 'explain_analyze'. The only implicit signal is that SELECT queries belong here, but there is no explicit when-to-use or when-not-to-use guidance.

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