submit_review_decision

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses the state machine (approved → done, changes_requested → pending or needs_human_review at retry cap) and the side effect that commit_hash is recorded on the latest attempt. It does not cover permissions, the actual retry-cap value, or return behavior.

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 compact and front-loaded, stating the purpose first then the branch consequences in a single dense passage with no wasted sentences. Density is high but every clause conveys actionable state-transition information.

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 state-transition coverage is solid, but gaps remain: the retry cap value is unspecified, as_agent semantics are unaddressed, and there is no indication of the response. Adequate but not fully complete given the tool's complexity.

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 0%, so the description must compensate, and it partially does: it documents the Decision enum values and explains CommitHash's conditional effect. However TaskId, Comments, and notably as_agent (which likely controls identity/auth context) are left entirely unexplained.

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 opens with a specific verb+resource ('a reviewer's verdict on a task in review'), which cleanly separates it from sibling verdict tools like submit_verification_verdict and submit_attempt_verdict that operate on findings/attempts rather than tasks. It never explicitly names those siblings, so differentiation is by inference rather than direct routing guidance.

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?

It clearly states the conditions and consequences for each decision branch (approved moves to done; changes_requested returns to pending or escalates at cap), which tells an agent when each value is appropriate. It stops short of naming alternative tools or stating prerequisites, so it is clear context without explicit exclusions.

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