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

With no annotations, the description carries the full burden and does substantial work: it names the exact evidence purchased (honeypot/owner-powers simulation, OFAC screen, page content, SEC profile, web results), the two-round/four-model argument, and the response shape. It also discloses the payment contract — an unpaid call returns an itemised quote for free, and pricing is $0.05–$0.12 per question. Missing latency, rate limits beyond the daily free call, and failure modes keeps it from a 5.

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?

Front-loaded with the core action ('Buys the FACTS first, then deliberates') and every following sentence adds distinct information — scanning logic, evidence types, deliberation structure, response contents, pricing. Slightly dense but no filler.

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?

No output schema exists, and the description compensates by stating the response lists every source and what was spent. Combined with the payment lifecycle and evidence scope, an agent has enough to invoke it correctly; only operational details like timing and rate limits are absent.

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 coverage is 100%, so the schema already documents q, x_payment and free_trial. The description reinforces the payment flow (unpaid call yields a free quote, which is what x_payment later settles) but adds no syntax or format detail beyond the schema, so the 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-and-resource action: buys evidence (contract/URL/ticker), then runs a 4-model, two-round deliberation. The 'grounded' positioning and the enumerated evidence types make it distinguishable from a plain council call, though it never names the siblings council or council_deep directly.

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?

Implied usage is clear — reach for this when the question hinges on a contract address, URL or $TICKER whose real-world evidence must be fetched. However, there is no explicit when-to-use/when-not guidance versus council or council_deep, so the agent must infer the routing from the word 'grounded'.

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