list_collections

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

With no annotations, the description carries the burden of disclosing behavior. It indicates this is a read-only listing operation ('list') and adds that results include counts, but it does not detail return shape, pagination, or any potential limitations. For a simple listing tool this is acceptable but not rich.

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, front-loaded sentence that conveys the core purpose and examples without any filler. Every element ('curated', 'perk-based', 'with counts') 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 parameterless listing tool, the description is mostly complete: it names the resource, gives examples, and mentions counts. However, it does not explicitly state the return format or whether counts represent numbers of related items (e.g., jobs), but this is reasonably inferable from the context.

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 is empty, so there are no parameters to describe. Baseline for zero parameters is 4; the description does not need to add parameter info because none exist.

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 lists curated perk-based collections, with specific examples and the inclusion of counts. This distinguishes it from sibling tools like list_categories by specifying the resource type (perk-based collections rather than general categories).

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 when one needs to retrieve curated perk-based collections, but provides no explicit guidance on when to prefer this over list_categories or other siblings. It would benefit from a phrase like 'use this for perk-based collections' or a note on how it differs from list_categories.

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