get_query_results_csv

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

Discloses caching behavior and refresh option; no annotations provided so description carries full burden. Could mention if CSV is returned inline or as download, but still transparent.

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?

Three sentences with no filler. Front-loaded with main action, efficiently provides key behavioral details.

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?

Adequate for a simple read tool with two parameters. No output schema, so format of CSV response is assumed. Could mention delivery mechanism, but overall complete for selection and invocation.

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 has 100% description coverage, but the description adds value by explaining the refresh parameter's effect (cached vs fresh) and the restriction on parameterized queries, which is not in 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 retrieves query results in CSV format, distinguishes itself from siblings like get_query (JSON) and execute_query (non-cached) by noting caching and refresh behavior, and explicitly states lack of parameterized query support.

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?

Provides explicit guidance on when to use refresh (true for latest data, false for cached) and explicitly notes unsupported parameterized queries, directing users to alternatives.

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