set_cell_autorefresh

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it delivers: it explains per-cell override semantics, engine-blocking of write cells, the `auto_refresh_blocked: "contains_write"` signal, markdown rejection, and the polling precondition. A mutation tool rarely gets this transparent.

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 dense but every sentence carries distinct information. Purpose and differentiation come first, followed by applicability, blocking behavior, and value semantics. There is no filler or repetition.

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 annotations and no output schema, the description is highly complete for a config setter: it explains the target, the alternatives, edge cases, and all value semantics. The only remaining gap is the lack of explicit definitions for `buffer_id` and `cell_id`, which are required parameters and left to inference.

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 compensate. It thoroughly documents `value` including true/false, fixed interval strings, and null-clearing behavior. However, `buffer_id` and `cell_id` are never explicitly described; their roles are only weakly implied by 'cell' and 'notebook default', leaving two of three required parameters under-specified.

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 states the exact action ('Set auto-refresh polling for a cell') and identifies it as a per-cell override of the notebook default, naming sibling set_notebook_autorefresh. This clearly differentiates it from the many cell-related and notebook-default sibling tools without ambiguity.

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?

It explicitly names the alternative tool (set_notebook_autorefresh) and gives concrete applicability rules: works for chart and grid cells, DDL/DML cells never poll, Markdown cells are rejected, and polling requires a per-cell value or notebook default. This is explicit when-to-use and when-not-to-use guidance.

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