export_query

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

Discloses key behavioral details: creates files locally, auto-adds timestamps to filenames, and returns local file path. However, it does not mention permission requirements, disk space concerns, or that it is a write operation (no annotations provided). Could be more explicit about side effects.

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 extremely concise: a single summary sentence followed by a bullet list of parameters. Every sentence adds value, and the structure is easy to parse. No wasted 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 no output schema, the description correctly identifies the return value (local file path). It covers the main functionality and parameter roles. However, it lacks details on error handling, file format specifics, or limits, which would be helpful for a tool of this complexity.

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?

Despite 0% schema parameter descriptions, the tool description compensates by listing each parameter with a brief explanation: sql is a SELECT statement, filename includes auto-timestamp, format specifies csv/json, database identifies the target, params is a parameter list. This adds essential meaning beyond the schema's type definitions.

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 executes a query and exports results to CSV or JSON, returning a local file path. This distinctively differentiates it from sibling tools like execute_query which return data directly, and list_databases which list resources.

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 like execute_query or execute_select. There is no mention of prerequisites or scenarios where this tool is preferred, leaving the agent to infer usage from the description alone.

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