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

Annotations already state readOnlyHint, openWorldHint:false, destructiveHint:false. The description adds pagination semantics (nextCursor, hasMore, totalCount) which tells the agent the operation is cursor-paginated and returns a total count - useful context beyond the annotations.

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?

One compact sentence with the core behavior and return shape front-loaded. Could arguably include one clause about scope (per-site/per-collection), but it does not waste words.

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?

Read-only and no output schema, and annotations cover safety. However usage guidance relative to sibling listing tools is absent, and the relationship between collection rows and pagination cursor is only implied. Adequate but with clear gaps.

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 id, slug, limit, and cursor including defaults and max. The description adds nothing param-specific, so baseline 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?

States the verb (page through) and resource (collection's rows), which is more specific than the title. However it does not distinguish itself from list_collections or get_collection, nor does it clarify the relationship to create_collection_rows/list_collections.

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?

No indication of when to use this versus list_collections, get_collection, or the sibling create/update row tools. The reader must infer that this is for paginated retrieval of rows within one collection.

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