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

With no annotations, the description carries the full burden and delivers: pricing band ($0.05–$0.12), the free unpaid-call quote, the 503-with-no-charge failure mode, the fact that sources and spend are itemised back, and the free-daily-call restriction to the quick tier. These are exactly the operational traits an agent cannot get from structured fields.

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 mechanic and generally dense with useful facts, but it repeats the address/URL/$TICKER scan condition twice and stacks several clauses per sentence, which slightly hurts scannability.

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, so the description must describe returns, and it does so adequately ('lists every source and what was spent'), plus failure and pricing semantics. Return format detail is thin but sufficient for a priced deliberation call.

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 baseline would be 3, but the description adds real meaning by tying 'q' to the address/URL/ticker requirement and by explaining the two-step payment cycle (unpaid call returns an itemised quote, paid call executes) that gives 'x_payment' its context.

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 mechanism: 'Buys the FACTS first, then deliberates,' naming the purchased evidence types (honeypot/owner-powers simulation, OFAC screen, page content, SEC profile) and the single-analyst judgement. The 'one analyst' phrasing implicitly distinguishes it from council_deep, but no sibling is named explicitly, so the differentiation is inferential rather than stated.

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 precondition is clear: the question must contain a contract address, URL or $TICKER, and without one the tool returns 503 and charges nothing. However, it never says when to choose this over sibling 'council' or 'council_deep' — the buyer must infer the trade-off from price and analyst count.

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