list_rows

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is covered. However, the description does not add any additional behavioral details beyond pagination defaults. It could mention that additionalProperties in schema is allowed (openWorldHint=false suggests no extra fields, but the schema allows them), but that's a schema issue, not description. Score 2 for lacking meaningful behavioral context beyond 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?

The description is a single sentence with essential information and no wasted words. Front-loaded with purpose and pagination defaults, followed by sibling alternatives.

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?

Given the low complexity (3 simple params, no output schema, annotations present), the description is nearly complete. It could mention that additionalProperties are allowed per schema, but that's minor. Annotations cover safety well.

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 detailed descriptions for each parameter (table name, page number, page size). The description only restates defaults, adding no new semantic value beyond what the schema already provides. 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?

The description clearly states 'List rows from a table with pagination', specifying the verb, resource, and key behavior. It distinguishes itself from sibling tools like find_rows (filtering/sorting) and query_sql (SQL queries).

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 explicitly tells when to use this tool ('use find_rows for filtering/sorting or query_sql for SQL queries'), providing clear guidance and alternatives.

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