superset_sqllab_export_csv

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

No annotations are provided, so the description carries the full burden. It does disclose a key environmental dependency (Results Backend), but it does not state whether the operation is read-only, what happens if the backend is missing, or any other side effects. This adds some but not comprehensive transparency.

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 concise and front-loaded with the main action, followed by an important prerequisite note and a structured Args section. Every sentence earns its place, with no redundant information.

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?

For a one-parameter export tool, the description covers the primary purpose, a critical prerequisite, and parameter provenance. The output schema likely handles return format details, so no further explanation is needed. However, it could more explicitly state the dependency on a prior execute call.

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?

The schema has 0% description coverage for the parameter, but the description compensates with an Args section explaining that client_id comes from superset_sqllab_execute. This provides meaningful provenance and purpose beyond the schema's bare 'string' type.

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's function with a specific verb ('Export') and resource ('query results to CSV format'). It also references the client_id from superset_sqllab_execute, which distinguishes this from other SQL Lab tools like superset_sqllab_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 provides a clear prerequisite (configured Results Backend) and indicates the client_id comes from a prior superset_sqllab_execute call, giving context on when to use the tool. However, it does not explicitly mention alternatives or when not to use it beyond the backend requirement.

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