query_database

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

The annotation readOnlyHint=true already indicates the tool is read-only. The description adds no further behavioral details such as authentication requirements, rate limits, or consequences. It simply repeats the read-only nature without 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 concise and front-loaded with the core purpose. It efficiently provides table names and examples in a structured format without unnecessary words.

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 presence of an output schema and annotations, the description is sufficiently complete for a read-only query tool. It could be slightly improved by mentioning query timeout limits or that DDL statements are blocked.

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 documents the 'sql' parameter with a description. The description adds value by listing available tables and providing examples, which helps the agent understand query patterns and constraints beyond the schema.

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 read-only SQL queries against the enterprise database. It specifies the verb 'run a read-only SQL query' and the resource 'enterprise database', distinguishing it from sibling tools that focus on specific reports or analyses.

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 for ad-hoc SQL queries but does not explicitly state when to use this tool versus alternatives like 'get_revenue_report' or 'analyze_sales_trend'. It lacks guidance on 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.