scroll_to_cell

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

With no annotations, the description minimally states the main behavior but fails to disclose side effects, limitations (e.g., does not select the cell), or constraints. An agent cannot assess safety or impact.

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 a single, concise sentence that is front-loaded with the key action. However, it could include more detail without adding length, such as parameter usage hints.

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 the tool's simplicity and presence of an output schema, the description is still insufficient. It omits parameter explanations, usage context, and differentiation from siblings, leaving an AI agent without enough information to invoke correctly.

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 has 0% description coverage, and the description adds no parameter guidance. Parameter names (cell_id, notebook, session_id) are moderately inferrable but the description does not clarify defaults or required context like which notebook is used when omitted.

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 uses a specific verb 'scroll' and resource 'notebook view' with object 'cell', clearly indicating the action. However, it does not explicitly differentiate from sibling tools like 'select_cell' which might overlap in purpose.

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 is provided on when to use this tool versus alternatives (e.g., select_cell, evaluate_cell). The description lacks context about prerequisites or use cases.

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