List items

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

Covers error handling (400 errors returned verbatim), pagination behavior (cursor, fetch_all auto-pagination capped at 20 pages), and field name convention. With no annotations, this provides good transparency.

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, no waste. First sentence states core purpose, second adds key details, third covers error handling. Well front-loaded.

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 pagination, error behavior, field names, nested variants, and inventory management. No output schema, but description provides enough for an AI agent to use correctly.

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 covers all 4 parameters (100% coverage). Description adds context: cursor pagination, fetch_all auto-pagination limit, error handling for 400. Adds meaning beyond 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?

Clearly states it lists items from Loyverse with the GET /items endpoint, mentions pagination, nested variants, and API version. Distinguishes from sibling list tools by focusing on items resource.

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?

No explicit when-to-use or alternative guidance. Context implies it's for listing items, but doesn't contrast with inventory or other list endpoints. Adequate but not explicit.

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