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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds substantive behavior beyond them: the score is a 0-100 scale, the inspection surfaces clearing reliability and Sybil wash-trade penalty flags, and the data lives on Base. It omits rate limits, auth requirements, and failure behavior for unknown agent IDs.

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?

A single dense sentence with no filler, and the core resource (trust score) is front-loaded before the secondary facets. Slightly cramped as an enumeration crammed into one clause, but nothing is wasted.

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 return-value burden and does so reasonably by naming the score range and the four data facets an agent will receive. Read-only annotations cover the safety side. Minor gap: it doesn't indicate what happens when an agent is unregistered or how the flags are presented.

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% — agentId (ERC-8004 token ID with an example) and chainId (Base mainnet/Sepolia) are fully documented in the schema. The description's only contribution is the phrase 'on Base', which loosely aligns with the chainId default but adds no new syntax or constraint.

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 ('Inspect') and resource (an AI agent's trust/reputation profile) and enumerates the facets returned: trust score, clearing reliability, Sybil flags, KYA backing. However, it never distinguishes itself from the sibling nullclear_verify_kya_mandate, whose domain ('corporate KYA backing') it explicitly overlaps.

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 — an agent can infer this is the read-only lookup to run before trusting or transacting with an agent, but the description gives no when-to-use trigger, no prerequisites, and no routing versus verify_kya_mandate or escrow_x402_call.

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