review_code

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses little: no mention of whether the review is read-only, whether findings are returned as text or structured issues, latency, or auth requirements. The enumerated focus areas hint at scope but not 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?

A single tight sentence with no filler. It front-loads the persona ('QA Engineer') rather than the action verb, which is a minor structural weakness for an agent scanning for the operation.

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?

There is no output schema, so the description should explain what a review returns (findings format, severity, or summary) and it does not. For an analysis tool with three parameters and no annotation coverage, the definition leaves the agent guessing about result shape.

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 100%, with all three parameters documented including examples for focus_areas, so the schema does the heavy lifting. The description adds nothing about parameter meaning beyond what the schema already provides, which is the baseline-3 case.

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?

Clear verb ('performs... code review') plus the resource ('code') and enumerates the review dimensions (bugs, security, edge cases, test coverage). It differentiates itself reasonably from analyze_codebase and suggest_improvements by framing the work as QA-style review, though it never names a sibling.

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?

No guidance on when to prefer this over suggest_improvements, analyze_codebase, or generate_tests, and no prerequisites or exclusion conditions are stated. The agent must infer usage from the tool name alone.

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