Read row list

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds the behavioral default 'Defaults to JSON,' which is useful. However, it does not mention any other behavioral traits (e.g., response size, pagination, or error conditions). With annotations present, this is adequate but not rich.

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: 'Return the content of a named row list within a table. Defaults to JSON.' It is front-loaded with the core action and object, and every word serves a purpose. No superfluous information.

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 simple read tool with 7 parameters and no output schema, the description provides the essential purpose but lacks context about the response structure (beyond JSON default) and how to apply the parameters. The rich schema compensates, but the description could be more complete for an agent deciding to use it.

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?

The input schema has 100% coverage with descriptions for all 7 parameters, so the description does not need to add parameter details. The description itself adds no extra meaning beyond the schema, which is the expected baseline for full schema coverage.

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 tool's function: 'Return the content of a named row list within a table.' This uses a specific verb and resource, distinguishing it from siblings like banana_rowlist_cell (single cell) and banana_table (full table). Adding 'Defaults to JSON' provides extra clarity about the output format.

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 gives no guidance on when to use this tool versus alternatives. It does not mention scenarios, exclusions, or contrast with the many sibling tools (e.g., banana_rowlist_names, banana_rowlist_cell). The agent is left to infer usage from the name alone.

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