nullclear_check_reputation

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

With no annotations, the description carries the full burden. 'Inspect' implies a non-mutating read and the enumerated fields partially compensate for the missing output schema, but it says nothing about authentication requirements, rate limits, whether results are cached/live, or what happens on an unknown agentId.

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 front-loaded sentence with no filler; every clause names a distinct returned signal. It is slightly run-on as a comma list, which mildly hurts scannability but wastes no words.

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 2-parameter read tool with no output schema and no annotations, the description usefully enumerates the returned signals and their 0-100 scale. However it leaves the behavioral contract (safety, auth, error cases) unstated, which is a real gap given zero annotation coverage.

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 agentId (ERC-8004 token ID) and chainId (Base mainnet/Sepolia) are already fully documented in the schema. The description adds only the vague phrase 'on Base', which the schema states more precisely, so 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?

States a specific verb ('Inspect') and enumerates exactly what is read: trust score with its 0-100 range, clearing reliability, Sybil wash-trade penalty flags, and KYA backing. It is clear on its own, but it does not differentiate from the sibling nullclear_verify_kya_mandate, which overlaps on the 'KYA backing' element.

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 gives no when-to-use guidance, no prerequisites, and never mentions the sibling tools (escrow_x402_call, verify_kya_mandate) or when one should be preferred over another. The only implied usage is that this is a read/lookup call.

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