tableau_view_csv

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

Describes important behaviors beyond annotations: client-side pagination, no server pagination, trimmed strings with null for empty, formatted amounts, error handling (429/5xx/404/thrown, schema_drift for gated views), and SSRF safeguards. Annotations only provide readOnlyHint and openWorldHint; description adds rich detail without contradiction.

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?

Long but densely informative; front-loaded with purpose. Every sentence adds context, though some redundancy exists (e.g., repeated emphasis on SSRF). Could be slightly more concise, but remains effective.

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?

Fully explains return format (view, columns, rows, _meta), error handling, honest pagination, and data integrity. No output schema, so description compensates thoroughly. Covers all likely agent questions.

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%, and description adds substantial context: view enum explained with example data and record count, limit/offset explained with meaning of totalAvailable (true row count) and client-side pagination. Goes well beyond schema 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?

Clearly states it fetches a complete CSV export from a Tableau Server Guest view, specifically for government transparency data. Provides an explicit example (mt_contracts_awarded) and distinguishes from sibling tools which focus on different data sources.

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?

Explains the context (SLED transparency, keyless access) and when to use (fetching government contract data from Tableau). Lacks explicit when-not-to-use or direct alternatives, but the sibling list and clear scope make usage context clear.

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