list_cells

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

Discloses important behavioral traits not inferable from schema or annotations: id stability vs. index, summary extraction, has_error meaning, and 0-based indices. No annotations provided, so description carries full burden.

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?

Concise and well-structured: purpose statement upfront, then list of returned fields, then clarifications on id and summary. Every sentence adds value.

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 single parameter and presence of output schema, the description fully explains the return fields and usage context. It covers what the agent needs to know for selection and 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?

Only parameter is 'path', but description adds no meaning beyond the schema. Schema description coverage is 0%, so the description should compensate but 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?

Clearly states it lists cells as a compact outline. Specifies return fields, implying a lightweight overview. Does not explicitly contrast with sibling 'read_cells', but the 'cheap overview' phrasing suggests it's a lighter alternative.

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?

Gives explicit usage guidance: 'Call this first to orient before editing.' However, it does not provide explicit when-not-to-use or alternatives like read_cells.

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