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

With no annotations, the description carries the full burden and does so well: it discloses replacement semantics, the one-verdict-per-reviewer constraint, revision pinning at submission, and staleness when report content changes. It omits auth/permission requirements (e.g. must the caller be a reviewer?) and error behavior, which keeps it from a 5.

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 core action and target are front-loaded in the first clause, with the optional note following, and the second sentence is dense but entirely substantive state semantics. Every sentence earns its place with no filler.

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 no annotations and no output schema, the description covers the important behavioral surface (replace, cardinality, snapshot/staleness). It stops short of describing return values or permission prerequisites, leaving a small but real gap.

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 only 67% and the verdict property has no schema description, so the description usefully supplies the two accepted values and constrains the note to a 'one-line' short string. It adds real meaning beyond the schema, though report_id is left to 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?

States a specific verb pair ('submit or replace') and an exact resource ('your review verdict on a report'), plus the allowed verdict values. An agent can distinguish this write tool from read-side siblings like get_report_signoffs and from adjacent actions like request_review or set_comment_status without opening a schema.

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 'submit or replace' framing makes the upsert semantics clear and tells the agent it does not need a separate delete/update step. It conveys clear usage context (one verdict per reviewer per report) but names no alternative tool and states no when-not-to-use condition, so it stops short of a 5.

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