Query Database

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully states that the tool is read-only and only allows SELECT statements, which is an important safety behavior. However, it provides no additional context about result format, error behavior, resource limits, or permission requirements.

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 two sentences with no filler. It front-loads the core purpose, then adds the critical restriction and usage guidance. Every sentence earns its place.

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 one-parameter tool, the description is largely complete: it explains what it does, the only allowed operation, and when to use it. The lack of an output schema is mitigated by the obvious nature of a SELECT query result, though explicit mention of return format would make it fully complete.

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 100%, so the SQL parameter is already well-documented. The description reinforces the 'SELECT' restriction but does not add significant new meaning beyond what the schema already provides. A baseline score of 3 is appropriate.

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 a specific verb ('Execute'), resource ('database'), and the exact nature of the operation ('read-only SQL query', 'Only SELECT'). It also distinguishes itself from sibling tools by noting it is for custom queries not covered by other tools, which is a strong 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?

The description gives clear usage context: use this for custom queries not covered by other tools. It states the read-only constraint, but does not explicitly list when not to use it or name specific alternative tools, though the 'not covered by other tools' phrase implies this.

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