EveBrief Risk Oracle (ERO)

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

Annotations only cover read/write safety; the description adds the things that actually determine behavior: a per-call price (0.01 RLUSD on XRPL or 0.01 USDC on Base), the two-step payment handshake, the verdict scale, the fact that findings separate on-chain facts from heuristics, and the guarantee that 'critical' requires on-chain proof. That is well beyond what readOnlyHint/openWorldHint convey.

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?

Dense but nearly every clause carries information an agent needs (price, payment retry, verdict levels, 'none' caveat). The one structural weakness is that billing mechanics lead the description ahead of the core 'what this does' statement, which is carried mainly by the title.

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 responsibly describes the return payload (verdict plus reasons and evidence, split into findings), and it explains the unusual x402 payment requirement that would otherwise cause silent failures. The only gap is not clarifying the relationship to get_methodology.

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 chain and address are already documented with format and pattern. The description adds nothing about parameter behavior (e.g. how a missing chain is inferred or which address types are eligible), so it sits at the baseline 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 — check an EVM address (token, deployer, wallet or contract) for rug-pull risk — and the return vocabulary (none/low/high/critical) makes the output shape concrete. It is unmistakably distinct from the sibling get_methodology, which explains scoring rather than scoring an address.

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?

Gives explicit procedural guidance for the paid flow: call without payment to obtain terms, then repeat with _meta["x402/payment"]. It also warns how to interpret a 'none' verdict. It does not say when to consult get_methodology instead of, or alongside, this tool, so full alternative routing is absent.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine but modest context beyond that: 'Free' indicates no cost/quota, and the phrase about risk levels, chain coverage and known limits discloses what the methodology covers. It does not disclose response format, size, or whether results are static documentation versus computed values.

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?

It is two short fragments with no filler, and the cost note is front-loaded. The terseness borders on cryptic — 'Free.' as a standalone sentence and a noun-phrase second sentence without a verb — but nothing is wasted or buried.

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 explaining what comes back; it names the topical contents (risk levels, chain coverage, limits) but not the form of the response (text document? JSON?) or how it relates to check_address verdicts. For a zero-parameter read-only tool that is adequate but leaves a real gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies a parameterless lookup rather than suggesting any inputs are needed.

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 name and title ('Get the ERO methodology') plus the phrases 'Risk levels, chain coverage and known limits of the verdicts' sketch out what the tool returns, but the description never states a concrete verb or object — it is a list of content fragments rather than a statement that this retrieves the documentation behind check_address verdicts. An agent can guess the purpose, but it must reconcile the name with the fragment list.

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?

There is no explicit when-to-use guidance and no mention of the sibling check_address, even though the natural usage is 'call this to understand what a check_address verdict means.' The only usage signal is the word 'Free,' which implies it is safe to call without cost but does not say when or why to call it.

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