Manage Iterations

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

Annotations declare the tool is not read-only, not idempotent, and non-destructive, but the description does not clarify which actions are reads versus writes. In particular, `assign_items` is a mutation, yet the description does not explain what it changes, whether it replaces or adds assignments, or what permissions are required.

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 short and front-loaded, listing the operations immediately and then explaining how to select one. It avoids waste, though it is arguably too terse given the tool's multi-action complexity.

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 tool with five actions, seven parameters, low schema description coverage, and no output schema, the description is missing critical details. It does not explain action-specific parameters, mutation behavior for `assign_items`, or what each operation returns.

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 only 14%, so the description must compensate but largely does not. It implies `date` for `get_by_date` and `itemIds` for `assign_items`, but leaves `fieldName`, `projectId`, `iterationId`, and `limit` unexplained and does not map parameters to actions.

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 names the specific resource (Project Iterations) and enumerates the operations: get configuration, current iteration, items, find by date, and assign items. This is clear enough to distinguish it from general project tools, though it does not explicitly differentiate it from similar siblings such as manage_sprints or manage_milestones.

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 only says to use the `action` field to select the operation, which is structural guidance rather than usage guidance. It does not explain when to choose each action, which parameters are required for each action, or when to use an alternative sibling tool.

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