post_test_result_comment

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that – no note that posting a comment is a permanent, non-idempotent write, and no indication of required permissions or what the response contains.

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 two sentences say the same thing twice; the second adds only a fragment. This is duplication rather than front-loaded structure, and it wastes the description budget on 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?

A destructive, non-idempotent write tool with nested parameters and no output schema needs more than a restated title. Nothing about permissions, payload shape, or the resulting comment/ID is provided.

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?

Both parameters are nested objects and the reported schema description coverage is 0% at that level. The description only vaguely gestures at the identifier ('using its unique identifier') without explaining the path/body nesting, the message length cap, or additionalProperties:false constraints. It adds essentially nothing over the schema.

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 two sentences are near-verbatim restatements of the tool name ('Post a comment on a test result'), with only a thin addition ('using its unique identifier'). It does not distinguish this tool from siblings like post_test_case_comment or post_issue_comment, so an agent gets no signal about which comment target this applies to beyond the name itself.

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 when-to-use guidance, no prerequisites, and no mention of the alternatives in the sibling list (post_issue_comment, post_test_case_comment). Usage must be inferred entirely from the tool name.

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