Neurons Reviews

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

The parenthetical "(and claim)" usefully discloses that this is not a pure read despite the "get" name, which is consistent with readOnlyHint=false and destructiveHint=false. But it does not say what claiming does to other users, whether claiming an already-claimed review fails, whether claiming is idempotent, or that the no-id listing path is read-only — meaningful gaps for a tool that mixes read and mutation.

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 clauses, front-loaded on the mode distinction, with nothing wasted. The telegraphic phrasing ("With id: ... Without: ...") is efficient but borders on cryptic, costing a 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?

A five-parameter, dual-mode tool with no output schema, no parameter descriptions, and mixed read/mutate behavior demands more than one sentence. Missing: the repo parameter's role, defaults for status/mine/claim, the claim-id dependency, and any hint of what the listing or claim result looks like.

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?

With 0% schema description coverage the description does the heavy lifting, and it explains id as the mode switch and names status and mine as list filters. It never mentions the repo parameter at all, gives no defaults (what happens with zero arguments?), and the claim parameter is only hinted at with "(and claim)" — the id+claim interaction an agent most needs is left unstated.

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 states the two modes concretely: with an id it retrieves (and optionally claims) a specific review, without an id it lists reviews. That dual-mode framing plus the named filters (status, mine) tells an agent what the tool does and roughly how it differs from siblings like review_request and review_submit. Minus one point because "open" is ambiguous (retrieve? create?) and the resource being operated on is only implied by the title.

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 keyed entirely to the presence of the id parameter, which is genuinely actionable guidance for choosing the mode. However, there is no mention of when to prefer this over review_request/review_submit/claims, and no prerequisites or exclusions are stated; usage is implied rather than spelled out.

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