exportQuery

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

With no annotations, the description fully discloses behavioral traits: read-only (SELECT only), streaming to file, no row-count limit, timeout controlled by environment variable, and format-specific options with defaults. This is comprehensive for a data export tool.

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 four sentences, front-loaded with the primary action. It is efficient but could be slightly more compact; however, no extraneous information is present.

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?

The description covers input parameters and behavior (streaming, timeout) but lacks details on error handling, file overwrite behavior, or permission requirements. For a tool with no output schema, this is fairly complete given its 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?

Schema coverage is 100%, but the description adds significant meaning: default values for CSV/JSON options, accepted keys, and timeout env variable. It explains formatting details beyond the schema's basic descriptions.

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 it executes a read-only SELECT query and streams results to a file, supporting CSV and JSON formats. This distinguishes it from sibling tools like query (returns results inline) and saveQueryEvidence (likely saves query evidence rather than results).

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 specifies it is designed for large datasets and streams to disk without row-count limit. It implicitly suggests use for exporting large result sets, but does not explicitly mention when not to use or alternatives like query for interactive results.

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