vtable_get_column_values

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

No annotations are provided, so the description carries the full burden. It discloses a significant behavioral nuance: raw=false returns rendered visual text whereas raw=true returns raw field values, and it mentions the return includes missing columns. It does not state explicit side effects or prerequisites but implies a read-only operation.

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 two sentences, front-loaded with the main purpose, and packed with essential information without any fluff or repetition. It effectively explains the tool's function, parameters, and return behavior.

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?

The description covers the core purpose, key parameters, and return summary, while the output schema provides formal return structure. It lacks explicit prerequisites or exclusions, but given the tool's relatively simple read nature, it is sufficiently complete.

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 compensates by explaining the key parameters: titles (array, with example) and raw (boolean, with behavioral difference). It omits iframe_selector, but that parameter has a default and is less user-facing.

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 reads all cell values in a column by Chinese title, using specific verbs and resource. This distinguishes it from sibling tools like vtable_get_cell_text (single cell) and vtable_get_all_records (all records).

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 clear context for when to use: to retrieve column values by title, with an explanation of the raw parameter's behavior. It does not explicitly name alternatives or exclusion cases, so it misses the top score but is still clear.

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