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

Annotations cover the safety profile (mutation, non-idempotent, non-destructive), and the description adds real behavioral context beyond them: the create-vs-update precondition, the QA server-side default for environment, the non-attaching behavior of FIND versus the attaching behavior of LINK, and the shape of the response. It doesn't say what happens to fields omitted on an update or what errors can occur.

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 dense sentences, front-loaded with the create/update rule before parameter detail. The trailing response-field list is lengthy and could be trimmed, but it is the only source of return-value information since there is no output schema.

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 an 11-param mutation tool with no output schema and thin schema descriptions, the description covers mode selection, required inputs, defaults, enum semantics, the FIND/LINK distinction, and the response fields. Only limitWhenNoPrior and update-merge semantics remain undocumented, which is a minor shortfall.

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?

With only 18% schema description coverage, the description does most of the work: it enumerates title, environment, dueDate, status, batchInvocationIds, release, id, and both commitRange modes with their distinct side effects. It leaves botId, projectApiKey (partly covered in schema), and especially limitWhenNoPrior unexplained, which is the main gap.

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?

Opens with a specific verb+resource pair ('Create or update a named test run') and immediately disambiguates the two modes via the 'Omit id to create' rule. The generic tool name 'manage-test-run' is fully compensated by this sentence.

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?

Gives a concrete mode-selection rule (omit id = create, and release is required in that case) plus guidance on when to pick FIND vs LINK for commitRange. It stops short of stating validation failures or when to prefer other tools, but no sibling covers test runs, so there are no real alternatives to route to.

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