Read Review

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Read the full content' without mentioning whether the file must exist, what happens if the filename is invalid, whether it returns raw markdown or parsed content, or any side effects. For a read operation this is a moderate gap, but the lack of any behavioral detail beyond the verb leaves the agent guessing about error behavior and return format.

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 with no waste. It front-loads the action and resource. However, it could have added a brief note about the return format or error behavior without becoming verbose.

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 has a single parameter, an output schema, and a clear read-only purpose, so the description is mostly adequate. However, with no annotations and no mention of what the output contains or how to handle missing files, an agent might not know what to expect when invoking it. The output schema likely covers return values, but the description doesn't reference 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 100%, so the schema already documents the filename parameter with a format hint. The description adds no additional meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 a specific verb ('Read') and resource ('REVIEW file'), which clearly identifies the tool's function. It doesn't explicitly differentiate from sibling tools like read_report or read_task, but the resource type is distinct enough that an agent can infer the difference.

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 implies usage context: use this tool when you need the full content of a review file. It doesn't explicitly state when not to use it or name alternatives like list_reviews for browsing reviews, but the context is reasonably clear given the sibling set.

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