Discogs: list marketplace orders

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

Annotations already declare readOnlyHint=true, and the description's 'List' operation aligns. The description adds the seller context and optional status filter, but does not reveal other behavioral aspects like pagination defaults, sorting options, or response structure. This is acceptable for a simple read-only list operation.

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 one concise sentence with no filler. It front-loads the primary action and resource, then adds the key modifier (status filter). Every word earns its place.

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 list operation with a well-defined schema and read-only annotation, the description covers the essential purpose and key modifier. It doesn't mention pagination or return format, but the schema covers the parameters and the tool's name indicates the resource. This is sufficiently complete for an agent to select and invoke it.

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 0%, so the description must compensate for parameter meaning. It only mentions the 'status' filter, while page, per_page, sort, and sort_order are left entirely to the schema. The schema is self-explanatory, but the description fails to add value beyond it for most parameters.

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', the exact resource 'marketplace orders', and the scope 'authenticated user's (as a seller)'. It distinguishes the tool from siblings like discogs_get_order (single order) and discogs_get_seller_inventory (inventory items).

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 clear context: it lists the authenticated seller's orders and supports an optional status filter. It doesn't explicitly name alternatives or when not to use it, but the seller scope implies a distinct use case from related order tools.

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