list_rows

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

Discloses behavioral traits: cursor pagination by row id, max limit 500, and presence of a version field. With no annotations provided, this description carries the full burden effectively, though error handling and auth are not mentioned.

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?

Two concise sentences, front-loaded with the main purpose. The version note is essential for update workflows and earns its place.

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?

With an output schema present, the description doesn't need to explain return values. It covers the key operational details (pagination, limit, version) adequately for a simple list tool.

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 has 0% description coverage. The description hints at limit ('Max limit 500') and cursor ('cursor-paginated'), and sheet_id via 'sheet's rows', but does not explicitly define each parameter or how cursor is used in practice.

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?

Clearly states 'List a sheet's rows' with specific pagination detail, distinguishing it from siblings like list_sheets and list_columns which target different resources.

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?

Provides context for when to use (listing rows) with cursor-pagination and max limit, and the version note suggests use before updates. However, no explicit exclusions or alternative tool mentions, though the resource-specific wording makes it evident.

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