set_cell_autorefresh

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

No annotations are provided, so the description carries the burden. It explains the semantics of the 'value' parameter (adaptive, off, or fixed interval), which is useful. However, it does not disclose side effects, prerequisites, or behavior when the cell is not in draw-mode.

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, well-structured sentences. The first states the action and target, the second details the parameter options in a compact format. No unnecessary words.

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 setter with no annotations or output schema, the description covers the core purpose and value semantics sufficiently for invocation. It could mention error cases or persistence, but these are not critical for basic use.

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?

The description thoroughly explains the 'value' parameter, including allowed boolean and string forms. However, it does not describe 'buffer_id' or 'cell_id', and the schema has no property descriptions. These are relatively self-explanatory identifiers, so partial compensation is sufficient.

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 action 'Set auto-refresh polling' for a specific resource 'a draw-mode cell's chart'. It distinguishes this tool from other set_cell_* siblings by focusing on auto-refresh behavior.

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?

Provides clear context that this applies to draw-mode cell charts, implying when it's relevant. Does not explicitly mention alternatives or when not to use, but the context is specific enough to guide selection.

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