list_releases

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

No annotations are present, so the description carries the behavioral disclosure burden. It explains the pagination envelope and the 'page again while next_page_results is true' pattern, which is valuable runtime behavior. It does not explicitly mention read-only semantics or auth, but 'list' strongly implies non-mutation.

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 front-loaded with the core purpose, then organized into Args and Returns sections. Every line is informative and there is no redundant or filler content.

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 paginated list tool, the description thoroughly covers pagination mechanics and the return envelope. It lacks optional details like sorting or filtering, but these are not indicated by the schema or context, so the description is sufficiently 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?

Schema coverage is 0%, but the description fully explains cursor ('Prior response's next_cursor; omit for first page') and per_page ('default 20'). This provides essential meaning beyond the bare schema types and defaults.

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 opens with 'List releases in the workspace (paginated)', giving a specific verb and resource. It clearly distinguishes itself from sibling tools like retrieve_release (single release) and create_release by focusing on the list operation.

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 explicit alternatives or when-not-to-use conditions are given. The pagination instructions (cursor, per_page, next_page_results) provide clear context for how to iterate, but the choice of this tool over retrieve_release is only implied by the name.

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