add_issues_to_cycle

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. The single sentence 'Add issues to a cycle' merely restates the tool's function and does not reveal whether issues are appended or replaced, what happens to existing cycle assignments, or any error conditions. This is essentially a tautology of the tool name.

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 concise sentence with no redundant words. It effectively states the core purpose without fluff, making it well-suited for quick comprehension.

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 mutating tool with no annotations and no output schema, the description is underspecified. It does not explain the outcome of adding issues that are already in the cycle, whether the operation is additive, or what the response might contain. The minimal description leaves critical operational context unanswered.

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?

The input schema already provides descriptions for all three parameters (project_id, cycle_id, issue_ids) with 100% coverage, so the description need not elaborate. The tool description adds no additional parameter-specific meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 'Add issues to a cycle' clearly states the action (add) and resource (cycle), and the phrase 'issues' clarifies the target. This distinguishes it from siblings like remove_issue_from_cycle and add_issues_to_module by explicitly naming the cycle context.

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 provides no guidance on when to use this tool versus alternatives such as remove_issue_from_cycle or add_issues_to_module. It only states the basic action without mentioning prerequisites, idempotency, or comparison with existing cycle membership behavior.

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