swu_collection_summary

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds context by specifying the summary scope and indicates a prerequisite (the collection must be loaded), but it does not explicitly state whether the tool is read-only, has side effects, or requires specific permissions. For a summarization tool, this is partially adequate but incomplete.

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 a single sentence that front-loads the purpose and lists the key output components. Every phrase adds value, with no wasted words 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?

The tool is simple with no parameters and an output schema present. The description covers the main output categories and the 'loaded' prerequisite. It could be more explicit about behavioral implications, but given the simplicity and existing output schema, it is largely 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?

The input schema has zero parameters, so there is no parameter documentation needed. The description appropriately focuses on output scope rather than parameters. Baseline for 0 params is 4.

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 'Summarize' and identifies the resource as 'the loaded Star Wars Unlimited collection', listing concrete output elements (total cards, unique printings, per-set breakdown, storage path). This clearly distinguishes it from siblings like swu_list_collection and swu_owned_count, which serve different purposes.

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 by describing a summary of the collection, but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites beyond 'loaded'. No comparative guidance is provided, so it earns a 3.

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