list_workitem_testcase_relations

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns relation records with specific fields and notes that relationRecordId is 'used for deletion', which adds useful context. However, it does not explicitly state that the operation is read-only, and it omits details about pagination, permissions, or error behavior. This is adequate but not thorough.

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 two concise sentences, front-loaded with the tool's purpose ('List test cases related to a work item'), and includes essential return-field information without any wasted words. It is well-structured and earns its length.

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 read/list tool with just two required parameters and no output schema, the description adequately covers the purpose and the return structure. It lacks explicit usage guidance and some behavioral details, but these are less critical given the low complexity and the presence of schema descriptions.

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 100% for both parameters, as both have descriptions in the input schema. The tool description itself adds no additional parameter-level information beyond what the schema already provides, so the baseline of 3 is appropriate.

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 tool lists test cases related to a work item, using a specific verb ('List'), a clear resource ('test cases related to a work item'), and further details the returned relation records and key fields (relationRecordId, testcaseId, subject, owner). This distinguishes it from sibling tools like create_workitem_testcase_relation and delete_workitem_testcase_relation.

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 implies usage for querying existing test case relations but does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions or alternative tools. The 'List' action makes the primary use obvious, but no explicit guidance is provided for when to prefer this tool over related list operations.

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