set_test_case_issues

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

No annotations are provided, and the description only states 'Set linked issues' without explaining effects like whether existing issues are replaced or appended, authentication requirements, or side effects. This leaves significant gaps in understanding tool behavior.

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 concise with a single sentence, but it is overly terse and lacks necessary detail. While there is no wasted text, the brevity undermines its 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?

Given the absence of annotations, no output schema, and an under-specified payload parameter, the description fails to provide sufficient contextual completeness. It does not explain the impact of the operation, return values, or structure of the payload.

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 50%; only testCaseId has a description. The payload parameter is described as an 'array of objects' with no further detail, and the description adds no additional meaning to the parameters. The incomplete schema and lack of elaboration reduce usefulness.

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 'Set linked issues for a test case' clearly states the verb and resource, making the tool's purpose understandable. However, it does not differentiate from sibling tools like 'add_test_case_external_links_bulk' or 'link_issue_to_defect', which could cause confusion for the AI agent.

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. There is no mention of prerequisites, context, or conditions under which this tool should be preferred.

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