recognize_cell_text

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

Discloses that background/reverse color is insensitive, a useful behavioral trait. But no annotations exist, and description does not cover empty cell behavior, error cases, or performance.

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?

Single sentence with essential info, front-loaded. Could be slightly improved with structured format but efficient overall.

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?

Adequate for a basic recognition tool with one parameter. Lacks details on return behavior for different cell types or error states, but output schema is absent so description is somewhat complete.

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 coverage is 100% with ref description. Description adds return format but no additional parameter meaning beyond schema. Baseline 3 applies.

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?

Description clearly states the tool recognizes cell text and returns text, bcolor, fcolor. It distinguishes itself from sibling tools like click_cell and input_cell that perform different actions.

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 tool versus alternatives like get_canvas_snapshot or quick_get_cell_bounds. Lacks explicit context for selection.

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