vtable_read_cells

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

With no annotations, the description carries the behavioral burden. It accurately conveys a non-mutating read and adds the row-major traversal behavior, but it does not disclose coordinate conventions, endpoint inclusivity, reversed range handling, or error behavior on out-of-bounds coordinates.

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?

A single well-structured sentence that front-loads the action and resource, then adds the relevant row-major detail. There is no filler or repetition.

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?

For a simple four-parameter read tool with an output schema, the description is nearly adequate, but it omits coordinate conventions and boundary-condition handling that an agent would need to call it correctly on unusual inputs. It also provides no guidance for choosing among the vtable siblings.

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?

Schema description coverage is 0%, so the description must compensate. It maps the four parameters to the two corners of a rectangle, which is meaningful, but it does not define bounds, inclusivity, or coordinate origin; the parameter names already suggest their column/row roles.

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 action (batch read) and the resource (rectangular region of cells), and it adds the row-major ordering detail. It does not explicitly contrast with sibling tools like vtable_cell_info or vtable_cell_resolve, so it stops short of full sibling differentiation.

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?

There is no guidance about when to use this tool instead of vtable_cell_info, vtable_cell_resolve, or other vtable siblings, and no exclusions or prerequisites. The intended selection context must be inferred entirely from the name and the sibling list.

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