get_cell_text_output

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as whether the tool is read-only, what happens on invalid index, or whether it truncates output. The max_length parameter is mentioned but without explanation of overflow behavior or defaults beyond 1500.

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 concise: a single clear sentence for purpose followed by parameter explanations. No redundant information, and the most important details are front-loaded.

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 retrieval tool without output schema, the description covers the main purpose and parameters. However, it could be enhanced by noting that the cell must have text output (not image) or that the output is a string. Overall, it is mostly complete given the tool's simplicity.

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 add meaning. It explains that 'index' is the cell index and 'max_length' is the maximum length, including the default. However, it does not specify whether index is zero-based, allowed ranges, or the behavior when max_length is exceeded.

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 (Get), resource (text output content of a specific code cell), and identifier (by index). It is distinct from sibling tools like get_image_output or get_cells_info which have different purposes.

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 implies the tool is for retrieving text output from a cell, but does not explicitly contrast with alternatives like get_image_output or mention restrictions (e.g., cell must have been executed). The context of sibling tools helps, but the description itself lacks explicit when/when-not guidance.

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