deleteIssueRelation

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

The annotations only indicate readOnlyHint=false, so the description should disclose behavioral aspects like permanence of deletion, required permissions, or impact on related data. It does none of this, merely restating that it deletes without any additional context.

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, but this is over-conciseness rather than efficient structure. It adds no value beyond the tool name, so it is not well-structured or informative. There is no front-loading of key details because there are no details.

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 nested pathParams, lack of output schema, and minimal annotations, the description is wholly inadequate. It provides no information about return values, side effects, or usage conditions, making it impossible for an agent to use this tool correctly without external knowledge.

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 0%, so the description must explain the parameters. It does not mention format or issueRelationId at all, leaving the agent to infer their meanings from names alone. This is a critical gap.

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 states the action 'Delete' and the resource 'issue relation' clearly. However, it does not differentiate from sibling tools like removeRelatedIssue or provide any context about what an issue relation is, so it scores a 4 rather than 5.

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?

No guidance is provided on when to use this tool versus alternatives such as removeRelatedIssue or when not to use it. There is no mention of prerequisites, side effects, or context that would help an agent decide to invoke this tool.

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