collection_summary

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The description indicates a read-only summarization operation, implying no side effects, but doesn't disclose what 'missing variants' refers to or how the summary is computed. It doesn't mention whether this covers all sets or requires prior filtering, or what the output looks like beyond a count.

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 efficient - a single sentence that conveys the core purpose. It's brief but not under-specified given the zero-parameter signature. Could potentially expand on the 'missing variants' behavior, but the current length is reasonable.

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 which helps define the return, and there are no parameters, so the description needs less. However, 'report missing variants' is ambiguous - missing from what reference? Does it require a target collection to compare against? Given the output schema is present but the concept of 'missing variants' is undefined, the description is somewhat incomplete for a fully self-contained 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?

The tool has 0 parameters, so there is no parameter semantics burden. The description fully conveys what the tool does given no inputs are needed. Baseline 4 is appropriate for a zero-parameter tool since there's nothing to document about inputs.

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 summarizes counts by set and rarity and reports missing variants. It specifies a clear verb (summarize), the resources (set, rarity), and an additional behavior (report missing variants). While it doesn't explicitly distinguish from siblings, the purpose is specific enough to identify its function among the collection-related tools.

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?

No guidance on when to use this tool vs alternatives. There are many collection tools (list_collection, value_collection, export_collection, get_set_statistics, get_set_completion_value) that could overlap. The description doesn't clarify when to use collection_summary vs list_collection or get_set_statistics, nor does it explain what 'missing variants' means in context.

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