execute_query

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

No annotations provided, so description must carry burden. Only states read-only and returns JSON. Lacks details on resource cost, error handling, or query language specifics. Output schema exists but is not referenced in description.

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?

Single sentence, 12 words, no fluff. Efficient but could benefit from more detail 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?

Despite having output schema, the description is too minimal. Given the tool's generality, it should explain usage context, query constraints, and relationship to siblings like query_at_snapshot. Incomplete for effective decision-making.

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?

Only parameter 'query' is a string with 0% schema description coverage. Description does not elaborate on expected SQL syntax, length limits, or formatting. Schema provides type only, description adds no value.

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?

Description clearly states verb 'execute', resource 'read-only SQL query on Trino', and output 'JSON'. Differentiates from siblings like explain_query or query_metadata_table by being general-purpose.

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?

Description implies usage for general read-only queries but does not explicitly state when to prefer this tool over siblings like query_at_snapshot or explain_query. No exclusions or alternatives mentioned.

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