execute_query

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions returning 'Query execution results' but does not disclose potential side effects (e.g., destructive SQL operations), access requirements, or safety implications of executing arbitrary SQL.

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 fairly concise, using a docstring-style format with Args and Returns sections. It avoids unnecessary repetition but could be slightly more concise by removing redundant headers.

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 complexity (raw SQL execution), lack of annotations, and sibling tools like execute_card, the description is incomplete. It does not address when to prefer raw SQL over saved cards, database compatibility, or output details despite an output schema being present.

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?

With 0% schema description coverage, the description must clarify parameter semantics. It briefly lists parameters ('database_id', 'query', 'native_parameters') but provides no detail on constraints, formats, or usage examples. 'native_parameters' is vaguely described as 'Optional parameters for the query' despite its complex 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?

Description clearly states 'Execute a native SQL query against a Metabase database', providing a specific verb and resource. This distinguishes it from siblings like execute_card, which runs saved queries, and list_databases, which retrieves metadata.

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 guidance on when to use this tool versus alternatives such as execute_card or other query methods. The description lacks explicit when/when-not advice or mentions of prerequisites.

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