download_table_csv

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

No annotations are provided, so the description must fully disclose behavior. It mentions the return format (dict with status, message, content) and the header parameter options, but it does not explicitly state that the tool is read-only or describe any potential side effects, rate limits, or size constraints.

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: a single main sentence followed by structured bullet points for prerequisites and arguments. Every sentence adds value without redundancy, making it easy to scan.

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 that an output schema exists, the description covers the return format (status, message, content) and explains prerequisites and parameter meanings. For a simple download tool, this is complete and provides sufficient context for an agent to use it correctly.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: doc_id (from list_documents), table_id (from list_tables), and header (with options label, id, none). This adds significant meaning beyond the schema's basic type and default.

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 purpose: 'Télécharge une table Grist au format CSV' (Downloads a Grist table in CSV format). It specifies the verb (download), resource (table), and format (CSV), distinguishing it from sibling tools like download_document_excel or download_document_sqlite.

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?

Prerequisites are explicitly listed: list_documents for doc_id and list_tables for table_id. This provides clear guidance on what to do before using the tool. However, it does not explicitly mention when to use this tool over alternative download tools (e.g., for Excel or SQLite), leaving some ambiguity.

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