List listings

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

Annotations already mark readOnlyHint, idempotentHint, destructiveHint=false. Description adds 'Read-only, changes nothing' and important details: rate limit of 25 requests/min, and that it returns empty list for employees' listings—beyond annotation coverage. No contradiction.

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?

Concise yet informative: spells out purpose, usage, filters, rate limit, and employee limitation in a few sentences. Front-loaded with main action and output fields. No unnecessary words.

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?

No output schema, but description lists returned fields. Could mention response is an array or pagination metadata, but given the simple list nature and annotations, it is sufficiently complete for most contexts.

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 description coverage is 100% with detailed descriptions for all 5 parameters. Description mentions pagination and filters generically but adds no new semantics beyond summarizing what schema already provides.

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 returns a LIST of authenticated user's listings with specific fields (id, status, category, link). Differentiates from sibling items_get_item_info for single listing details. Specific verb 'Returns a LIST' and resource described.

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: 'Use it to find listing ids and get an overview; for details on a single listing, use items_get_item_info.' Also mentions limitation with employees' listings and rate limit, providing comprehensive guidance.

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