List row lists

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 that the result is a JSON array with an example format, but does not disclose behavior for edge cases like missing tables or empty row list sets. Given the safe read annotation, the added context is modest.

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, clear sentence with an example, front-loaded and concise. Every element contributes; no filler.

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 listing tool with good annotations and full schema parameter coverage, the description sufficiently conveys the output format. It could mention error scenarios or empty results, but given the tool's simplicity, the current description is nearly 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 clear parameter descriptions for 'table' and 'doc'. The description does not add further parameter detail, but the schema already fully explains the inputs, so the baseline score of 3 is appropriate.

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 precisely states the tool returns a JSON array of row list names for a given table, with an example. This clearly distinguishes it from sibling tools like banana_table_names (which lists table names) and banana_rowlist (which deals with row list contents).

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 simply by stating what it does, but it does not explicitly explain when to use this tool over alternatives. No mention of exclusions or prerequisites such as the need for an existing table.

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