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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering safety. The description adds pagination semantics (cursor, hasMore, totalCount) and a default/max limit, which is useful beyond the annotations, but omits rate limits or ordering of results.

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 front-loading the return fields and paging behavior, then limits. No padding.

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?

A read-only list tool with no output schema; the description names returned fields (rows, nextCursor, hasMore, totalCount), which compensates for the missing output schema. But it leaves slug/site_id semantics and any filtering behavior unexplained, and gives no guidance on starting or ending paging.

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 only 25% (only cursor is documented in schema), so the description carries extra burden. It supplies the limit default (50) and cap (200), aiding the limit param, though slug and site_id remain undocumented.

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 a specific verb+resource (list a collection's rows) and clarifies it's a paged listing. Distinguishes from list_collections and from sibling writers like create_collection_rows/update_collection_row, though it doesn't name an alternative directly.

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 when-to-use guidance. Nothing tells the agent when to page with this vs. get_collection or how to begin paging; the cursor param implies iteration but no instructions are given.

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