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

The annotations already establish that this is a non-destructive read operation with open-world access. The description adds useful return context by naming the review fields (who verified it, verdict, when), but it does not explain auth scoping, id semantics, or what happens when no review exists.

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 definition is a single short phrase with no filler, and the parenthetical efficiently packs the return fields. It is slightly weakened by being a noun fragment rather than a complete directive.

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 simple read tool, annotations cover the safety profile and the description gives some return shape. However, with no output schema and no schema parameter description, the definition omits id semantics and edge cases such as missing reviews, leaving real 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?

The sole required parameter, id, has 0% schema description coverage, and the description never mentions or defines it. The phrase 'one of your proposals' implies selection but gives no meaning to the identifier.

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 fragment identifies the resource (a single proposal) and the payload (its review, including verifier, verdict, and time). It is clear enough to infer retrieval, but it does not use an action verb or explicitly name the sibling list tool for differentiation.

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?

There is no guidance on when to call this tool versus source_proposals or other source_* siblings. It also omits prerequisites such as needing a proposal id or whether the proposal must belong to the caller.

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