listReleases

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

No annotations are provided, so the description carries the burden. It discloses that the tool lists git tags from the bridge and not software releases, which sets expectations about the data source and scope. However, it does not mention read-only behavior, authentication needs, or the role of the 'relays' parameter, leaving some behavioral gaps.

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 is direct and front-loaded with the verb 'List'. It includes a necessary qualifier about what it is not, without any redundant words.

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 simple list tool, the description conveys the core function and a key distinction from related tools. It does not explain return format or relay usage, but the schema covers limit and default behavior. Given the lack of an output schema, the description is adequate but could mention the relays parameter.

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 75% (3 of 4 parameters have descriptions). The description itself does not add parameter-level meaning beyond what the schema provides. The 'relays' parameter is left undocumented in both the schema and description, so the agent gets no clarification on its purpose.

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 action ('List') and the resource ('git tags from the bridge (refs/tags/*)'), and explicitly distinguishes from 'Zapstore software releases'. This specificity differentiates it from sibling tools like createRelease or fetchForgeReleases.

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 'not Zapstore software releases' clause provides a clear exclusion, guiding the agent to avoid this tool for software release operations. However, no alternative tool is explicitly named, so the guidance is clear on context but not fully explicit with alternative suggestions.

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