Elements List Workbook Columns

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint. The description adds valuable behavior beyond them: it automatically pages to the last page and specifies the returned keys entries, total, nextPage null, and hasMore false where applicable.

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 purpose is front-loaded in the first sentence, and the second sentence explains pagination and return shape. The pagination sentence is dense but each clause serves a purpose, with no filler.

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?

An output schema exists, so return values do not need full explanation, and annotations cover safety. However, the description omits parameter semantics and explicit sibling routing, leaving gaps for an agent choosing and invoking the tool.

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?

There is only one required parameter, workbook_id, but the schema provides no description and the tool description never explains its format, source, or semantics. With 0% schema description coverage, the description should compensate and does not.

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?

States a specific verb and resource: list all columns across all elements in a workbook, including formulas and types. The scope 'across all elements' distinguishes it from the single-element sibling elements_get_element_columns and from workbooks_list_report_columns.

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 scope implies when the tool is appropriate, but the description never names alternatives such as elements_get_element_columns for a single element or workbooks_list_report_columns for reports. It provides context but no explicit exclusions or routing.

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