read_cell_outputs

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

With no annotations, the description carries full responsibility for behavioral disclosure. It merely states 'returns outputs' without detailing whether it blocks, handles large outputs, or any side effects. The presence of 'maxBytes' and 'normalize' parameters hints at behavior, but the description does not explain them.

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 extremely concise, consisting of a single sentence. While brevity is valued, it sacrifices necessary detail, making it barely adequate for an agent to understand the tool's functionality.

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 the high number of sibling tools and the lack of output schema, annotations, or parameter descriptions, the description is incomplete. It does not explain the return format, error conditions, or special behaviors like output truncation (implied by maxBytes).

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 schema has 0% description coverage, and the tool description adds no information about the parameters 'cellIds', 'maxBytes', or 'normalize'. The parameter names and types provide minimal self-documentation, but the description should clarify their purpose and constraints.

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 verb 'returns' and the resource 'outputs for selected cells', making the tool's purpose unambiguous. It effectively distinguishes from sibling tools like 'get_cell' (metadata) and 'watch_cell_outputs' (streaming).

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, expected context, or when to prefer a sibling like 'watch_cell_outputs' or 'get_cell'. The description is too sparse to help the agent decide among related tools.

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