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 burden for behavioral disclosure. 'Add issues to a cycle' implies a mutation operation but provides no information about permissions required, whether this is idempotent, what happens if issues are already in the cycle, error conditions, or what the response looks like. For a mutation tool with zero annotation coverage, this is inadequate behavioral transparency.

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 extremely concise at just four words with no wasted language. It's front-loaded with the core action and doesn't contain any unnecessary elaboration. While it's arguably too brief for adequate tool documentation, it scores perfectly on the conciseness dimension as defined.

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?

Given this is a mutation tool with no annotations, no output schema, and sibling tools that perform related operations, the description is insufficiently complete. It doesn't explain what happens after issues are added, whether there are constraints on which issues can be added, or how this interacts with other cycle operations. For a tool that modifies data, more context is needed.

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 schema description coverage is 100%, with all three parameters clearly documented in the schema. The description adds no additional parameter information beyond what's already in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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' is a tautology that essentially restates the tool name. While it identifies the verb ('add') and resource ('issues to a cycle'), it lacks specificity about what this operation entails and doesn't differentiate from sibling tools like 'remove-issue-from-cycle' or 'list-cycle-issues'. It's minimally informative but doesn't provide meaningful context beyond the obvious.

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. With sibling tools like 'remove-issue-from-cycle', 'list-cycle-issues', and 'create-cycle', there's no indication of when this specific add operation is appropriate versus other cycle-related operations. There's no mention of prerequisites, constraints, or typical use cases.

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