Link tasks

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

Annotations indicate modification and idempotency; description adds details about cycle rejection and parameter effects, going beyond annotations without contradiction.

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 concise sentences, front-loaded with the main verb, no redundancy, each part adds value.

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?

Covers purpose, kind variants, and a behavioral constraint (cycle rejection). Missing return value info but acceptable given no output schema and good annotations.

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?

Explains ticket and linkedIssue roles and kind enum, but does not describe the project parameter. With 0% schema coverage, more explanation of all parameters would be better.

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?

Description clearly states it relates two tickets, explains the two kinds with examples, and distinguishes from sibling tools that perform different operations.

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?

Explicitly describes when to use each kind ('linked' vs 'blocks'), including cycle rejection. Could be improved by noting when not to use this tool, but alternatives are not available in siblings.

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