delete_workitem_testcase_relation

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

The destructiveHint annotation already flags destructiveness, and the description adds the specific object being removed and how to source the relationRecordId. It doesn't discuss reversibility or side effects, but the annotation plus targeted description cover the main behavioral trait.

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?

One single sentence, front-loaded with the category and containing a clear action, target, and parameter-source hint. No filler or redundant content.

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 three-required-param destructive tool with a destructiveHint annotation and no output schema, the description is functionally complete: it covers what is removed and where the required relation ID comes from. It doesn't include error behavior or permission requirements, but these are not essential here.

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 descriptions cover 100% of parameters, so the baseline is 3. The description's mention that relationRecordId comes from list_workitem_testcase_relations is useful but largely repeats the schema's 'list or create' provenance note.

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 uses specific verb 'Remove' with clear resource 'test case relation from a work item' and identifies the key parameter (relationRecordId). It clearly differentiates from sibling create/list_workitem_testcase_relations tools.

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 that relationRecordId must be obtained from list_workitem_testcase_relations, providing clear prerequisite context. It doesn't explicitly discuss when not to use it or mention create_workitem_testcase_relation as the alternative, but the usage context is clear.

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