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 transparency burden. It mentions 'using DeepSeek', which implies an external AI service, but does not disclose that code is sent to a third party, potential privacy/data-sensitivity implications, or operational details like rate limits, latency, or failure modes. For a tool that exfiltrates code to an external model, this is a significant transparency gap.

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 sentence, front-loaded with the action ('Review a single file or code snippet') and ends with the model ('using DeepSeek'). Every word carries meaning; there is no filler or repetition.

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 and no annotations, so the description must cover return values, side effects, and prerequisites. It fails to explain that code is sent to an external AI service, what the output format looks like, or any limitations (e.g., file size, model required). This is incomplete for a tool that makes an external API call, especially given the presence of sibling review tools that could be confused with it.

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 input schema already provides descriptions for all 5 parameters, achieving 100% schema coverage. The tool description adds no additional parameter-level semantics beyond the schema, so the baseline score of 3 applies.

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 the clear verb 'review' with a specific resource ('single file or code snippet') and scope (bugs, quality, best practices). It distinguishes itself from sibling tools like review_folder, review_project, review_security, and review_performance by focusing on a single file or snippet and a general review scope.

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 clearly states the tool is for a single file or code snippet, providing context on when to use it. However, it does not explicitly mention alternatives like 'review_folder' or 'review_project' for larger scopes, nor does it state when not to use it. The single-file scope is a clear contextual cue, but the absence of exclusions or alternative references keeps it from a 5.

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