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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds substantive context the annotations cannot: that the read is free with no payment challenge, the exact facts surfaced, and the equivalent HTTP endpoint. It stops short of saying what happens for an unknown operator id.

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 purpose and returned fields are front-loaded, which is good. However the payment point is repeated three times in one sentence ('FREE — no payment required: call directly without payment (no x402 challenge; this tool is free)'), diluting an otherwise tight description.

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 does the needed work by listing the reputation facts returned and pre-empting the 'where is the score' question. Remaining gaps — id format and not-found behavior — are minor for a single-parameter read 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?

There is a single required parameter 'id' with 0% schema description coverage, so the schema itself is silent. The HTTP-equivalent URL ('/operators/{id}') implies the id is an operator identifier, which compensates partially, but the expected format (slug, address, numeric id) and lookup failure behavior are left undocumented.

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 and resource ('read an operator's reputation facts from their public profile') and enumerates the concrete fields returned (verified, tenure_days, tier, strikes, proposal rights). It clarifies that no separate score exists, which prevents the agent from hunting for one, but it never names the closest siblings (commons_get_operator, reputation_check) to differentiate scope.

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 does give actionable calling guidance — this tool is free, requires no x402 payment, and can be called directly — but that is invocation mechanics, not selection guidance. It never says when to prefer this over commons_get_operator or reputation_check, so the agent must infer the distinction.

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