notebook_read_cell_output

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

With no annotations, the description carries the burden. It correctly indicates a read operation (no destruction), but lacks details on whether the cell must have been executed, what happens if output is empty, any size limits, or whether it retrieves all output types (text, images, etc.). Decent but not comprehensive.

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?

Extremely concise: a single sentence that immediately conveys the action, target, and scope. No wasted words or redundant information.

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 no output schema and moderate complexity (reading potentially large output from a specific cell), the description is minimal. It explains enough to use the tool at a basic level but omits behavioral details an agent might need (e.g., return format, execution state requirements). Just adequate.

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 coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema property descriptions. For a simple read tool with only two parameters, this is acceptable but does not add value.

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 'Reads the output list of a specific code cell', using specific verb+resource to distinguish reading output from other cell operations. However, it does not emphasize how it differs from notebook_read_cell (which likely reads the cell source/input) or notebook_edit_cell_output, and the large sibling set makes this ambiguity notable.

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 on when to use this tool versus alternatives like notebook_read_cell, notebook_edit_cell_output, or notebook_read_cell_metadata. The agent must infer that 'output' differentiates it from reading the cell's source code, but no explicit context, prerequisites (e.g., cell must be executed), or exclusions are provided.

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