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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral value beyond them: 'Transaction verification is always false' discloses a data characteristic the agent would otherwise misread, and the untrusted-data warning is an explicit safety directive. It stops short of describing pagination, size limits, or return shape.

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?

Three short sentences, each carrying distinct information: purpose, a data caveat, and a handling rule. The purpose is front-loaded and there is no filler.

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 single-parameter read tool whose annotations already carry the safety profile, the description covers purpose, a non-obvious data caveat, and a prompt-injection warning. The only gap is the undocumented merchant_id and the absence of any note on result volume, which is minor here.

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?

There is one parameter (merchant_id) with 0% schema description coverage, and the description does not mention it at all. While merchant_id is fairly self-explanatory, the description adds no meaning about its format, source, or what happens if it is invalid.

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?

States a specific verb (read) and resource (feedback/reputation) with a scoping qualifier ('grouped by evidence basis'). It is understandable on its own, but it never names or contrasts with any sibling tool (e.g., get_preparation, prepare_review), so differentiation is left to the name.

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 offers no when-to-use context, prerequisites, or alternatives. Nothing tells the agent when get_reputation is the right call versus the other review-related siblings, so usage must be inferred entirely from the tool name.

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