query_one

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

Without annotations, the description must disclose all behavioral traits. It indicates a read operation but does not specify that SELECT statements might be arbitrary SQL (potential injection risk) or whether there are any side effects. The 'first row' concept is undefined regarding ordering, which is a significant gap.

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 very concise with a single sentence, but it sacrifices completeness. While front-loaded with 'Run', it omits crucial details. It could be slightly longer to include essential info without becoming verbose.

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 output schema, the description should explain the return format (e.g., object, array). It does not clarify 'first row' semantics (ordering) nor mention the database and connection parameters. The sibling list suggests many query tools, but the description does not differentiate sufficiently.

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 50%, but the description adds no additional meaning to parameters. The required 'sql' and optional 'params' lack descriptions in both schema and description, leaving their purpose ambiguous. The description does not compensate for the missing parameter documentation.

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 verb 'Run a SELECT' and specifies it returns only the first row. This distinguishes it from siblings like 'query' which likely returns all rows, providing clear purpose differentiation.

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 explicit guidance on when to use this tool versus alternatives such as 'query' or 'count'. The description only implies usage for single-row retrieval, but does not mention when not to use it or what alternatives exist.

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