delete_issue_relation

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

The description only states that it deletes a relation. It does not disclose whether the operation is idempotent, if it errors on nonexistent relations, or any side effects. With no annotations, the description carries the full burden but fails to provide sufficient behavioral 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 a single, grammatically correct sentence with no redundant words. However, it may be too brief for a delete operation, lacking important 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 tool's simplicity (1 required parameter, no output schema, no annotations), the description is minimally adequate but does not cover safety or existence checks. It is incomplete in terms of behavioral context.

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 describes the parameter 'id' as 'Numeric relation ID to delete' (100% coverage). The description adds no additional meaning beyond what the schema provides.

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 'Deletes an issue relation' clearly states the verb (deletes) and the resource (issue relation). The tool name also matches, and it distinguishes itself from sibling delete tools by specifying the object type.

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 like deleting an issue or a relation type. There is no mention of prerequisites or scenarios where this action is appropriate.

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