review_backend

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results are heuristic, that middleware may fall outside scope, and that verification is required — real limitations. But it omits whether the tool is read-only, what 'supported' backends/languages are, and how results are presented, leaving meaningful gaps for a code-review operation.

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?

Two tightly written sentences with the scope and risk list front-loaded and the caveat placed last where it belongs. Nothing is redundant, though 'supported backend source' is a slightly vague qualifier that costs a little precision.

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 3-parameter review tool with no annotations and no output schema, the description covers scope and caveats but says nothing about parameter usage, what findings look like, or how pagination works. An agent can pick the tool but not confidently invoke 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?

Schema description coverage is 0% and there are three parameters (path, limit, offset), all undocumented in both schema and description. The description gives no indication that 'path' scopes the review or that limit/offset paginate it, so an agent must guess that pagination even exists.

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 ('Review') and resource ('backend source') and enumerates the risk classes it inspects: route authorization, query construction, error handling, configuration. It distinguishes itself loosely from review_frontend by scope, but never names or contrasts siblings like review_security, which overlaps the same risk territory.

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?

Usage is implied by the backend/frontend split in the sibling set, and the closing caveat signals that findings are heuristic and need verification. However there is no explicit when-to-use statement, no condition for choosing this over review_security, and no prerequisites for invocation.

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