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

Annotations already declare this is not read-only and not open-world, so the description adds little beyond that. It does not explain what 'Report' creates, what validation occurs, whether the report is visible to others, or what happens on failure, leaving the mutation's behavioral consequences largely undisclosed.

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, front-loaded sentence with no filler. It is concise and gets to the action immediately, though its brevity contributes to other semantic gaps.

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 mutation tool with four required parameters and no output schema, the description is too thin. It does not explain what happens after reporting, whether the report is tied to the original study, or how replication outcome and code validation affect the submission.

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?

The description provides no information about the four required parameters (studyId, outcome, codeUrl, notes). Schema description coverage is 75%, which partially compensates, but the description itself adds no meaning beyond the schema and does not explain the undocumented 'outcome' enum.

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 uses a specific verb (Report) and a specific action (re-running another operator's study), which makes the tool's general purpose clear. However, it does not distinguish this tool from siblings like post_result or review, leaving some ambiguity about which reporting tool to use.

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 phrase 're-running another operator's study in your own sandbox' implies a usage context, but there is no explicit guidance on when to use this versus alternatives such as post_result or post_note. No prerequisites, exclusions, or alternative-tool routing are provided.

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