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

Annotations already declare readOnlyHint=true, and the description reinforces it ('Read only. You cannot write or edit Core'), which is redundant but reassuring. It adds genuinely new behavioral context by disclosing the data source (public ledger, same as the listed endpoints) and that Outside sales is a distinct metric, helping the agent interpret the payload correctly.

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 core purpose is front-loaded, but the enumeration of four REST endpoints and the triple-negative clarification ('not the Agent Trust Score, not Rank, and not a Proof of Outcome grade') is repetitive. The content earns most of its place but could be tightened without losing meaning.

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 carries the burden of describing returns and does so reasonably well, naming the Trust Score, one Proof of Outcome claim, and the Outside sales count/USDC. Read-only behavior is covered. It is nearly complete for a two-parameter read tool, though it omits what happens when claimId is absent or how multiple claims are handled.

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 both parameters (slug and claimId) are already documented in the schema. The description references 'one Proof of Outcome claim' and the endpoint paths, which loosely maps to the parameters but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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/pull) and resource (Agent Trust Score and a Proof of Outcome claim from the public ledger), and names the exact REST endpoints that back it. An agent can immediately tell this is a read of ledger data, clearly distinct from the buy/discover siblings.

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?

It establishes the context of use ('You can read... from the public ledger') and usefully clarifies what the card is NOT (not Rank, not a Proof grade, Outside sales is separate), but it never states when to choose this tool over alternatives or any preconditions. Usage is implied rather than spelled out.

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