review.get

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns JSON but does not mention error handling, permissions, or behavior when the ID does not exist. The read-only nature is implied but not explicit.

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, front-loaded sentence in Korean: 'Retrieves the detailed JSON of a specific review_id.' No unnecessary words or repetition of the tool name.

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?

The tool is simple (one parameter, no output schema, no annotations). The description explains the main purpose and identifies the parameter, but missing details such as error responses and authentication. This is adequate but not complete for a tool with no structured metadata.

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 schema only defines 'id' as a string with minLength 1, with no description. The description adds that this is a review_id, giving context. However, it does not explain the format or origin of the ID. With 0% schema coverage, the compensation is minimal but some value is added.

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 clearly states the tool retrieves the detailed JSON of a specific review_id, using the verb '조회' (retrieve) and the resource 'review'. This distinguishes it from siblings like review.list by specifying a single review ID.

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 '특정 review_id' implies use when a specific review ID is known, as opposed to listing all reviews. No explicit alternatives are named, but the context is clear enough for a simple getter tool.

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