list_columns

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

With no annotations, the description must disclose behavior fully. It only states it 'list[s] all columns' but omits key behaviors: that it supports pagination (via limit and page_token), optional filtering (visible_only), and is a read-only operation. The output schema exists but does not compensate for missing behavioral context.

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 a single, clear sentence with no redundancy. It efficiently conveys the core purpose, even though it lacks detail in other dimensions. It is front-loaded with the action and object.

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?

Despite the presence of an output schema, the description is incomplete for a tool with 5 parameters (2 required, 3 optional). It does not explain pagination behavior, the effect of 'visible_only', or how to use the tool effectively. More context is needed for correct 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?

The input schema has 0% description coverage, and the tool description adds no parameter-specific information. It does not explain that 'doc_id' is the document identifier, 'table_id_or_name' selects the table, or how 'limit', 'page_token', and 'visible_only' affect results.

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 uses a specific verb ('list') and resource ('columns in a table'), and specifies the scope ('all'). It distinguishes from sibling tools like 'get_column' (single column) and 'list_tables' (tables). The addition of 'with their properties, formats, and formulas' clarifies the return content.

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 no guidance on when to use this tool versus alternatives, such as when to use 'get_column' for a single column or how pagination works. There are no prerequisites or exclusions mentioned.

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