Raise a review comment on the paper

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

With no annotations, the description carries the burden. It discloses that by default the comment is a 'suggestion' awaiting human acceptance, and only with accepted:true in copilot mode is it immediately actionable. It mentions the workspace and author loop. It does not cover edge cases or side effects, but the main behavioral trait is well explained.

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 three sentences, front-loads the core action, and every sentence adds necessary context. No fluff or repetition. Efficient and to the point.

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?

No output schema is provided, but the description does not mention what the tool returns (e.g., a comment ID). It also doesn't clarify that the page parameter defaults to 1 (though schema says so). For a creation tool, omitting return value information is a gap. However, the description sufficiently covers invocation behavior.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the accepted parameter's effect and default behavior, which goes beyond the schema description. It also implies the role parameter implicitly with 'reviewer agent' but does not elaborate on the enum values, so not fully compensating but still adding value.

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 clearly states the action (post a review comment), the resource (anchored to a passage of the paper), and the agent (reviewer). It distinguishes from leaving 'one long critique' and implies this tool is for targeted comments, separating it from siblings like reply_to_comment.

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 description says when to use: 'leave many targeted comments rather than one long critique.' It explains the accepted parameter's context: only in fully-autonomous mode. However, it doesn't explicitly contrast with siblings like reply_to_comment or resolve_comment, though the name and description imply this is for new comments.

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