read_spreadsheet_cell

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the manager never sees cell text in binary render, a targeted read re-evaluates the cell, and the flow opens a form and runs a report before navigating. It also names the return shape, though it omits permissions or re-entrancy concerns.

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 purpose is front-loaded, but the body is dense, jargon-heavy and mixes English with Cyrillic, making it harder for an agent to parse quickly. Several clauses (wire-decode details, byte-shape `0x9a<len>`) expand without changing the calling decision.

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?

An output schema exists, so return values need not be detailed (though they are). For a tool with deep internal protocol nuance and zero annotation coverage, the definition covers mechanism well but leaves the majority of parameters unexplained, leaving gaps an agent must guess at.

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 0% and only the `address` parameter is meaningfully explained (R1C1 notation, arbitrary length, navigate frame resizes). The other five parameters — host, port, field, capture, captured_address — are undocumented in both the schema and the description, so the compensation is only partial.

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 and resource ('Read a spreadsheet CELL by address natively') and contrasts it with the binary .mxl wire-decode approach, which clarifies what the tool is not. It does not, however, distinguish itself from close siblings like read_table_cell or read_record.

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?

The description explains the internal mechanism (targeted in-client read, replayed form/report flow) but never states when to pick this tool over read_table_cell, read_list_row, or read_record. There is no when-to-use, when-not-to-use, or alternative routing guidance.

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