List Project Iterations

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so safety is covered. The description adds genuinely new behavioral context: the plan requirement (Premium/Ultimate) and the fact that results are drawn from the group hierarchy rather than only the project. It does not cover pagination or result ordering, but with annotations present this is a solid addition.

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?

Two short sentences, front-loaded with the core purpose and the scope caveat, with no wasted prose. The trailing "Premium/Ultimate." fragment is terse but readable and conveys a real constraint.

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 9-parameter listing tool with no output schema and no documented parameters, the description is thin: it omits pagination controls, the date-filter semantics, and what a returned iteration actually contains. An agent would need to inspect the schema to call this correctly, and the schema itself has no descriptions.

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 0% across 9 parameters, so the description carries the full burden. It merely enumerates filter names (state, search, search_in, include_ancestors, date filters) without explaining values, formats, or effect — search_in's accepted values and include_ancestors' hierarchy-walking behavior are left undefined. page, per_page and project_id are not mentioned at all.

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?

"List iterations available to a project (those of its group hierarchy)" states a specific verb plus resource and clarifies the scope derives from the group hierarchy. This implicitly separates it from the group-level sibling, though it never names gitlab_list_group_iterations explicitly.

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 tool's context is implied by "available to a project" and the Premium/Ultimate note tells the agent the feature is plan-gated. Beyond that there is no explicit guidance on when to pick this over the group-level iterations tool, nor any exclusion or prerequisite for include_ancestors.

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