get_review

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

With no annotations, the description carries the full behavioral burden. It implies a read-only call by saying it avoids creating another capture and discloses that before/after states are returned, but says nothing about permissions, error/not-found behavior, or what the states contain.

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 a single front-loaded sentence with no filler, which is good, but the wording is circular and nonstandard ('native capture task states'), so the brevity comes at the cost of clarity rather than earning its place.

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 one-param retrieval tool with no annotations and no output schema, the description should at least explain the review_id and the returned shape. Instead it omits both and does not clearly route the agent among the several review/capture siblings, leaving meaningful gaps.

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% and the single parameter 'review_id' is undocumented in both the schema and the description. The description does not explain what a review_id refers to, where to obtain one, or how it relates to captures, so the param is effectively opaque.

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?

It names a verb ('Return') and a resource ('before/after native capture task states'), but the resource is oddly phrased and does not clearly correspond to the tool name 'get_review' or to a review object, leaving the actual payload ambiguous. An agent cannot confidently tell what get_review retrieves versus siblings like capture_review or review_quality.

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 phrase 'without creating another capture' implicitly contrasts this call with capture_review, hinting that it should be used to read existing state rather than create one. However, it never states the condition or when-not explicitly, and there is no mention of prerequisites or alternatives by name.

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