Get Collection Items

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

Annotations already indicate read-only, idempotent, non-destructive operations. The description adds key behavioral context about pagination: 'one page at a time' and how to use the footer value for subsequent pages. This goes beyond annotation data.

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 concise and front-loaded: a one-sentence summary followed by crisp argument documentation. No filler, every sentence adds value.

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?

For a paginated read tool with an output schema and comprehensive annotations, the description covers purpose, parameters, and pagination mechanics. The footer-based paging detail is especially valuable for correct invocation.

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?

The input schema has no property descriptions (0% coverage), but the description's Args section fully explains all three parameters: collection_id (collection key), limit (max items per page with default and max), and start (offset mechanism). This completely compensates for the schema gap.

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 'Get items in a specific collection, one page at a time.' It specifies the verb (get), resource (items), and scope (specific collection), distinguishing it from siblings like get_recent_items which returns recent items across the library.

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 provides explicit context: use this tool to browse items in a specific collection with pagination. It doesn't explicitly mention alternatives, but the use case is clear enough that an agent can infer when to select it over similar tools.

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