post_test_run

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

Annotations already disclose the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true), so the bar is lower, but the description adds no behavioral context beyond that: no mention of side effects, required identifiers, permission needs, or that a new run is non-idempotent and cannot be repeated safely.

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?

It is short and front-loaded, which is good, but the second sentence is pure redundancy rather than earning its place. The available brevity is spent on repetition instead of on the missing usage or behavioral details.

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 creation mutation with a deeply nested body and no output schema, the description should at minimum indicate what is required (name, milestone_id) and what the call yields. Nothing about the payload, the resulting resource, or failure conditions is provided, so an agent must rely entirely on the schema and annotations.

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 description coverage is reported at 0% and the description adds nothing about the body payload. Although the nested properties (name, milestone_id, users, test_cases, etc.) are individually documented inside the schema, the description itself contributes no parameter meaning, so it fails to compensate for the coverage 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?

The description names a specific verb and resource ('Create a test run'), so the basic action is clear, but the second sentence simply restates the first with the added locator 'within a project'. It offers no differentiation from the many other creation siblings such as post_test_case, post_test_environment, or post_test_result.

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?

There is no guidance on when to use this tool versus alternatives (e.g., clone_test_run, post_batch_update_test_runs) or what preconditions exist. The only contextual hint is 'within a project', which is implied usage at best and does not tell an agent when not to use it.

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