list_items

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

With no annotations provided, the description carries full burden. It discloses pagination behavior (1-indexed page, returns metadata) and filtering (case-insensitive contains), but doesn't mention rate limits, authentication needs, error conditions, or whether this is a read-only operation (though 'List' implies safe read).

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?

Well-structured with a clear summary sentence followed by Args/Returns sections. Every sentence adds value, though the Returns section could be slightly more concise given the output schema exists.

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?

Good completeness for a list tool: purpose, parameters, and return structure are documented. With output schema present, the Returns description is somewhat redundant but helpful. Missing behavioral aspects like error handling or performance characteristics keep it from a 5.

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?

With 0% schema description coverage, the description fully compensates by explaining all 3 parameters: page (1-indexed), page_size (items per page), and filter_name (case-insensitive contains, optional). It adds crucial semantic details not in the bare schema.

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 the verb 'List' and resource 'items', specifying optional filtering and pagination. It distinguishes from siblings like get_item (single item) and create_item/update_item/delete_item (mutations), but doesn't explicitly contrast with search or other list variants that might exist.

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 implies usage for retrieving multiple items with filtering/pagination, but doesn't explicitly state when to use this vs. get_item (single item) or when filtering/pagination is appropriate. No alternatives or exclusions are mentioned.

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