List releases

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

With no annotations, the description carries the transparency burden. It discloses sort order (newest-first by release_date), the fields returned, and the filter semantics (substring, case-insensitive). It omits explicit statement of read-only nature, but the 'List' verb implies it and no side effects are expected for a list operation.

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 three sentences long, front-loaded with the core purpose, followed by return fields and usage guidance. Every sentence serves a distinct function with no redundant filler.

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 no output schema, the description usefully lists returned fields and order. All four parameters are fully documented in the schema, so the description doesn't need to repeat them. Minor gap: the 'track + EP' terminology is not reconciled with the schema's 'single-track releases', but this is a minor ambiguity.

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 100%, so baseline is 3. The description adds no substantive parameter meaning beyond the schema; it merely recounts the stage filter with slightly different common values. It does not mention limit, includeEps, or includeTracks, but the schema already documents these fully.

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 track + EP releases from the Berbotu vault, with a specific resource and scope. It distinguishes itself from sibling list_demos by focusing on releases, and the verb 'List' is specific.

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 gives explicit 'Use this when' triggers, including label catalog, scheduled releases, what's coming out, and 'anything about releases'. However, it does not explicitly mention when not to use it or compare to the sibling tool list_demos, so it falls short of full alternative guidance.

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