list_group_iterations

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'List group iterations with filtering options,' which conveys that the operation is read-only, but it does not mention important behaviors such as default ancestor inclusion, pagination behavior, output shape, or permission requirements.

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 with no wasted words. It is appropriately concise for a straightforward list tool, though it is terse and does not preview the richer parameter schema below.

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?

The tool has ten optional parameters, no annotations, and no output schema, so the description alone is somewhat thin. However, the input schema thoroughly explains every parameter, making the definition adequate for invocation. Missing output and behavioral context prevent a higher score.

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 the schema fully documents all ten parameters with types, defaults, and allowed values. The description adds no parameter-level meaning beyond the generic phrase 'with filtering options,' so the baseline of 3 applies.

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 verb ('List'), the resource ('group iterations'), and the general capability ('with filtering options'). It is unambiguous and distinct from all sibling tools, which target different resources such as milestones, issues, releases, or projects.

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 makes the intended use case clear: use this tool when you need to list group iterations. It does not explicitly name alternatives or when-not-to-use conditions, but no sibling tool competes for this exact purpose, so the context is sufficiently clear.

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