swu_list_collection

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

With no annotations, the description carries the full burden. The verb 'List' signals a read-only operation, 'from the loaded collection' implies a prerequisite, and 'Pass limit=0 for no limit' discloses non-obvious behavior beyond the schema default. However, it doesn't specify error behavior if no collection is loaded or how results are ordered.

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 two sentences with the main purpose up front and a concise parameter tip. Every word earns its place; there is no fluff or redundancy.

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?

An output schema exists, so return format is already covered. The description addresses the core listing purpose, the optional filter, and the limit edge case. It lacks explicit guidance on alternatives or edge-case error handling, but for a simple list tool with a loaded-collection precondition, it is nearly complete.

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. It adds meaning to both parameters: set_code is described as an optional filter, and limit is given a special value '0' meaning no limit. This is valuable beyond the bare type/default info in the 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 uses the specific verb 'List' and identifies the resource as 'owned printings from the loaded collection', with an optional filter by set_code. This clearly distinguishes it from sibling tools like swu_owned_count (which likely counts) and swu_search_cards (which searches broadly).

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 context by stating 'from the loaded collection', indicating this tool operates on an already-loaded collection. It also provides parameter guidance with 'Pass limit=0 for no limit'. However, it does not explicitly name alternatives or explain when not to use this tool, such as when a count or summary would be more appropriate.

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