delete_workitem_testcase_relation

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

The annotation destructiveHint=true already discloses the destructive nature, and the description's 'Remove' is consistent. It adds context by specifying the ID source and that it removes a relationship, but does not disclose further side effects or return behavior, which is acceptable given the annotation coverage.

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, concise sentence with a clear category prefix and no filler. It efficiently communicates the action, target, and key identifier without redundancy.

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 deletion tool with three fully documented parameters and no output schema, the description is sufficient. It covers the action, the required identifier, and the prerequisite for obtaining it, while the annotation handles the destructive nature and the schema handles parameter details.

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?

All three parameters are fully described in the schema (100% coverage), including relationRecordId's origin from list/create operations. The description's mention of relationRecordId adds no new meaning beyond what the schema already provides, so it relies on the schema's parameter documentation.

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 clearly states the action ('Remove') and the target ('test case relation from a work item'), making it easily distinguishable from create/list sibling tools. It also specifies the key parameter (relationRecordId), providing a precise and unambiguous purpose.

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 indicates a prerequisite by stating relationRecordId is obtained from list_workitem_testcase_relations, guiding the agent on how to prepare for this tool. However, it does not explicitly discuss when not to use it or compare with the create/update alternatives, so it lacks explicit exclusions.

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