notebook_read_cell_output

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

With no annotations, the description fully carries the transparency burden. It discloses that outputs are saved from the last execution and lists possible output types. It correctly implies a read-only, non-destructive operation. Missing explicit mention that no execution is triggered, but still adequate.

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?

Two concise paragraphs: first states purpose and return types, second details parameters. Every sentence adds value; no fluff. Front-loaded with the most critical 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?

With an output schema likely defining return structure, the description doesn't need exhaustive details. It covers the essential: what outputs contain, when they are available, and how to specify the cell. Tool is fully described given its complexity.

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 0%, but the description's 'Args' section fully describes both parameters: notebook_path (relative path) and cell_index (zero-based index). This adds meaning beyond the schema titles and compensates for the lack of schema-level descriptions.

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 'read' and resource 'saved outputs of a code cell'. It distinguishes from siblings like notebook_read_cell and notebook_read_metadata by explicitly stating it reads outputs, not cell content or metadata.

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: outputs are saved from the last run and are empty until execution. However, it does not explicitly compare to alternatives or state when not to use it, so it stops short of a 5.

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