swu_load_collection

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

No annotations are provided, so the description carries the full burden. It explicitly discloses that the tool 'persists to disk' and that merge=False (default) implies replacing the existing collection, which is a destructive behavior. This is important behavioral context, though it doesn't mention validation or error handling.

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?

Two sentences with no wasted words. It front-loads the action and includes the essential file format and merge behavior. Perfectly concise for the tool's complexity.

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?

Given the tool's simplicity (2 params, output schema exists) and the presence of sibling tools, the description covers the core functionality well. It doesn't elaborate on return values (handled by output schema) or edge cases, but these are not critical for a straightforward import tool.

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 explain parameters. It explains csv_path as the CSV export with specified columns, and merge=False default behavior via 'set merge=True to add to existing collection instead of replacing it.' Both parameters are addressed, though the exact path format and CSV encoding are not detailed.

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 tool imports a Star Wars Unlimited collection from a SWUDB CSV export, specifying the exact columns (Set, CardNumber, Count, IsFoil) and that it persists to disk. This distinguishes it from siblings like swu_list_collection (listing) and swu_upload_deck (deck-specific upload).

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 for when to use the tool (importing from CSV) and gives a specific usage instruction: set merge=True to add to an existing collection instead of replacing it. It doesn't name alternative tools explicitly, but the merge guidance helps decide between add and replace modes.

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