Read row list cell

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to repeat safety. It adds no additional behavioral details beyond the read-only return of a value, and does not mention potential edge cases (e.g., row not found). This is minimally adequate given annotation coverage.

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 one concise sentence, front-loaded with the core action ('Return the value') and includes all necessary scoping in a clear order. Every word earns its place.

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 read-only cell retrieval tool with no output schema, the description is complete enough. It specifies the identification components and the result ('value'), and the schema covers parameter details. Slightly more context about return type or error behavior could be added, but it is not necessary given the simple nature.

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 100%, so the schema already documents each parameter. The description does not add meaning beyond restating the parameter roles. Baseline 3 is appropriate when the schema carries the burden.

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 operation: 'Return the value of a single cell within a named row list' and identifies the key resource identifiers (table, row list, row selector, column XML name). This distinguishes it from sibling tools like banana_rowlist (returns whole list) or banana_cell (likely for table cells).

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 context by specifying the exact parameters needed, but it does not explicitly state when to use this tool over alternatives or mention any exclusions. For example, it does not say 'to read a single cell, use this; to read entire rowlist, use banana_rowlist'.

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