runQuery

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

The description is extremely brief and fails to disclose any behavioral traits beyond the basic action. For a SQL execution tool, critical information such as whether it executes DDL/DML, potential destructive effects, idempotency, or permission requirements is missing. No annotations provide additional context.

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 short and front-loaded, but it is overly terse. Every sentence does earn its place, but the brevity comes at the cost of essential information, making it only moderately concise.

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 tool's complexity (SQL execution) and the lack of annotations or output schema, the description is grossly inadequate. It does not explain what the tool returns, whether it is read-only, or how to handle errors, leaving an agent with insufficient context for safe use.

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?

The input schema covers all three parameters with descriptions, so schema_description_coverage is 100%. The description adds no additional meaning beyond what the schema provides; it only restates the existence of the parameters implicitly.

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 tool runs a SQL query, specifying the verb 'Runs' and resource 'SQL query on the target system'. However, 'target system' is vague and doesn't distinguish it from other database-related tools like tableContents.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites, limitations, or when not to use it.

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