query

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

With no annotations, the description bears full burden for behavioral disclosure. It only notes 'read-only', which is a key trait, but fails to describe error handling, response format, or what happens on invalid SQL. No info on permissions or rate limits.

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 10-word sentence that front-loads the key action and read-only constraint. Every word is purposeful, with no fluff.

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 the lack of output schema and annotations, the description is sparse. It does not explain return values, error behavior, or the effect of the optional connectionString override. For a database query tool, more detail would be expected for completeness.

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% (both parameters have descriptions in the schema). The description adds no additional meaning beyond what the schema provides; it only mentions 'currently connected database' which is tangentially related to the connectionString parameter but does not clarify its usage.

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 'Run a read-only SQL query against the currently connected database', specifying the verb 'run', the resource 'SQL query', and the read-only nature, which distinguishes it from potential write operations. The sibling tools are 'connect' and 'disconnect', making 'query' obviously the data retrieval tool.

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 implies usage when a connection is already established ('against the currently connected database'), providing context that the tool requires a prior connection. However, it does not explicitly state when to use alternatives like 'connect' or 'disconnect', though the sibling names make this obvious. No exclusive guidance is given.

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