hex-get-cell-output

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

With no annotations, the description carries the full behavioral burden. It flags the unstable API status, which is genuinely useful, but says nothing about permissions, whether output may be absent for unrun cells, or rate limits.

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 short sentences with the unstable-API caveat front-loaded in parentheses. Efficient, though 'Returns the output of a cell' largely restates the name.

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 tool whose entire value is its return value, there is no output schema and no description of the output format (text, HTML, error objects, etc.), nor handling of cells that have never run. Incomplete for its purpose.

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?

One parameter (cellId) with 0% schema description coverage, and the description does not explain it at all—no format, source, or how to obtain a valid cellId. The description adds nothing beyond the parameter name.

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?

States a specific verb (Get) and resource (cell output) that clearly differentiates it from hex-get-cell and hex-list-cells. It's clear what it does, though it doesn't compare itself to siblings explicitly.

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 versus hex-get-cell or other cell tools. The '(unstable API)' note hints at caution but gives no conditions for selection or prerequisites.

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