Get Cell Content

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. This description only states the basic operation and does not disclose return format, error handling, or edge cases like out-of-bounds coordinates. It adds no behavioral context beyond what the tool name already suggests.

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, front-loaded sentence with no unnecessary words. It is concise and easy to parse, appropriately sized for the simplicity of the tool.

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 has three required parameters, no annotations, and no output schema, the description is too sparse to be complete. It fails to explain parameter semantics, return values, or usage context, leaving significant gaps that could confuse an agent attempting to invoke the tool 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 description coverage is 0%, so the description is responsible for compensating, but it does not explain any parameters. It does not clarify whether row/col are zero-indexed, what format tableId expects, or what the return value looks like. This leaves the agent without meaningful parameter guidance.

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 'Read text of a table cell' uses a specific verb (read) and resource (table cell), making it clear what the tool does. It also distinguishes itself from the sibling 'set_cell_content' by clearly indicating a read operation rather than a write operation.

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 implies usage when you need to read text from a cell, but it does not explicitly state when to use this tool over alternatives, nor does it provide exclusions. It is a self-contained read operation, but there is no mention of alternatives or when-not-to-use, so it relies on implication.

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