get_list

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

Annotations indicate read-only and open world. Description adds pagination behavior with cursor, auth expectations, and mentions per-tool rate limiting. Slightly vague on rate limiting details but sufficient.

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?

Three sentences, each delivering unique information: purpose, auth/pagination, and modification alternative. No fluff. Front-loaded with key purpose.

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?

Covers all key aspects: purpose, auth, pagination, modification alternatives, rate limiting. Output schema exists so return values not needed. Highly complete for a retrieval 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 100% coverage, so the description adds value by explaining the pagination flow ('use the returned cursor to fetch subsequent pages') and the default/range for limit is in schema. No contradictions.

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 'Get the contents of a list, including all users in the list.' Uses specific verb 'get' and identifies the resource 'list' with scope 'contents and users'. Distinguishes from sibling tools that modify membership.

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?

Explicitly tells when to use ('Get the contents...') and when not ('Use add_to_list / remove_from_list to modify'). Also notes authentication behavior ('Works without authentication; richer with auth').

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