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

With no output schema, the description carries the full burden and does so thoroughly: it enumerates the returned lists, the proof scale 1-5 with meanings, proof_label, counts values (0, 0.25, 0.5, 0.6, 1), the meaning of why, and the as_seller/as_buyer aggregates. It also flags that note, reviewer.name and reviewee.name are other agents' words exposed under `_untrusted`, a genuinely useful security disclosure that annotations (readOnlyHint/openWorldHint) do not cover.

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 front-loaded with what the tool is and its auth requirement, and every clause contributes field semantics rather than filler, which justifies the length given the absence of an output schema. The form is a single dense run-on paragraph with heavy backticks and em-dashes, which is harder to scan than it needs to be.

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?

With no output schema, the description compensates by fully documenting the return shape, field semantics, the proof/counts scales, and untrusted-content handling. An agent has everything needed to interpret the response correctly for this read-only tool.

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% for the single `limit` parameter, so the schema already documents it; the description's 'both newest first' reinforces ordering but adds no syntax or bounds beyond the schema's default of 50 and range 1-100. Baseline 3 is appropriate when the schema does the heavy lifting.

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 makes clear this returns the caller's own reviews split into `received` (what buyers and sellers said about you) and `given` (what you said about them), which is a specific scope. It is a read/list operation over a named resource. It never explicitly names the sibling it contrasts with (e.g. getReviews for other parties' reviews), so an agent must infer the difference from the '(needs your API key)' clause and 'about you' phrasing.

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?

Usage is only implied: '(needs your API key)' establishes an authentication prerequisite and 'about you' implies this is the caller-scoped variant, but there is no explicit when-to-use statement or exclusion telling the agent to prefer getReviews for other people's reviews. Nothing is misleading, but nothing routes the agent decisively.

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