list_columns

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

The description explains the return structure (success, message, columns) and implies a read operation. While no annotations exist, the description is transparent about behavior, though it does not explicitly state it is read-only.

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?

Structured with clear sections (Prérequis, Flux de travail typique, Voir aussi, Args, Returns), every sentence is informative and no excessive wording, making it concise yet complete.

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 the tool's simplicity and the presence of an output schema, the description covers prerequisites, workflow, parameters, and returns comprehensively, leaving no gaps for an AI agent.

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 coverage, the description adds meaning by defining parameters ('doc_id: L'ID du document', 'table_id: L'ID de la table') and integrates them into the workflow, fully compensating for the schema's lack of details.

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 'Liste toutes les colonnes dans une table Grist', providing a specific verb ('list') and resource ('columns'), and distinguishes it from siblings like 'create_column' by specifying the action.

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?

Explicitly lists prerequisites ('list_tables'), provides a typical workflow (1. list_tables, 2. list_columns, 3. list_records), and references alternative tools ('create_column', 'modify_column') under 'Voir aussi', guiding when to use this tool.

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