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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new context by disclosing data provenance ('served from the Escro database, which mirrors Escro's on-chain escrows') and the absence of an aggregate score — both important for interpreting results. It stops short of stating refresh cadence or what happens for wallets with no history.

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?

Two tight sentences: the return payload and its components come first, followed by the data-source caveat and the no-composite-score warning. No filler, no repetition of the title, and the most decision-relevant constraint is front-loaded.

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 one-parameter read tool with rich annotations and no output schema, the description covers what is returned, where it comes from, and the key caveat that no aggregate score is provided. The remaining gap is structural detail — units and ranges for delivery time, volume, or age — but that is a minor omission at this complexity.

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 wallet parameter at 100% schema coverage, and the schema already specifies 'Base-58 wallet address' plus the no-composite-score note. The description adds no format examples, chain assumptions, or failure behavior for malformed/unknown addresses, so it is a baseline case where the schema does the work.

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 ('Fetch one wallet's EscroRep raw components') and enumerates exactly what comes back: completion, disputes, delivery time, volume, age. It also clarifies the scope ('one wallet') and explicitly rules out a composite score, so an agent knows this is a raw-data lookup rather than a scored verdict.

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 line 'No composite score: weigh the components yourself' implies the intended use case (agent performs its own assessment) and implicitly steers away from expecting a ready-made rating. However, it never states when to use this versus the sibling tools (get_escrow, list_escrows) or any prerequisites such as needing an existing escrow history.

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