delete_work_package_relation

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

Confirms 'permanently delete' and clarifies it does not delete either work package, adding context beyond annotations which only mark destructiveHint=true. IdempotentHint not discussed but not contradictory.

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 sentences, front-loaded with action, no redundant words. Efficient and clear.

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?

For a simple deletion tool with no output schema and annotations covering destructiveness, the description is sufficient. Could mention return value or error conditions, but not essential.

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 coverage is 0% (no parameter description). Description implies id is the relation ID via usage guidance, but does not explicitly state parameter semantics. Adequate for a single simple parameter.

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?

Clear verb 'delete' and specific resource 'work package relation'. Explicitly distinguishes from deleting work packages themselves, which aligns with sibling tool delete_work_package.

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?

States prerequisite: use only after list_work_package_relations confirms the relation ID. Consequence described as destructive change removing dependency. Lacks explicit exclusions or alternatives.

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