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

The description adds behavioral details beyond the readOnlyHint annotation by explaining the non-streaming nature of MCP and the polling mechanism. It also discloses the return shape with rows, next_cursor, and has_more. It does not mention auth or rate limits, but those are not critical for a read-only operation.

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 two sentences long, immediately states the core purpose, and includes the return shape and a key usage pattern. Every sentence earns its place with no redundancy.

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?

The description covers the return structure and polling/pagination behavior, which is essential for this type of tool. The existence of a list_deleted_rows sibling implies this lists non-deleted rows, though that is not explicitly stated. Overall, it is sufficiently complete for a read-only list operation.

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?

All four parameters are described in the schema with 100% coverage, so the baseline is 3. The description reinforces the polling use of `since` but the schema already states it is a poll handle. No additional parameter semantics are provided.

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 lists rows in a v2 app's mutable collection, using a specific verb and resource. It distinguishes itself from sibling tools like get_row (single row) and delete_row/update_row/upsert_row (mutations).

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?

It explicitly explains that this tool is also the way to poll a collection's current state, and instructs passing the prior next_cursor as `since` for incremental fetching. This provides clear guidance on when to use this tool versus alternatives for tracking changes.

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