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

Goes well beyond the annotations by disclosing the pricing model (reuse tier, about ¢2, priced as a share of replaced tokens, typically 40–60k, shown as saves.tokens), the exact failure mode of an unpaid call (status=payment_required with rails, accepts, saves and a retry block), and that stubs are free. That is precisely the billing/permission context annotations cannot express.

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?

Three information-dense sentences, front-loaded with what is returned before pricing and the payment-required path. No filler, though the packed parenthetical enumerations make it heavier to parse than necessary.

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-shape burden and does so by naming the payload sections, plus it explains the payment negotiation cycle. The main gap is routing: it never says when to call this instead of sibling read tools such as match, thin, density or answer.

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 slug, pow_nonce, pow_challenge, x_payment and work_token. The description adds flow context for the payment path (payment_required result, retry block, free stubs) but no field-level semantics 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: reads the 'sealed oracle pack for a slug' and returns it as 'deterministic JSON', then enumerates the payload (markdown, claims with byte-exact quotes and spans, source CIDs, licence, receipts, review, labels, strength). It is clearly distinguished from write-ish siblings like attest or work, though the jargon 'sealed oracle pack' and 'reuse tier' are not explained in plain terms.

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: the slug is 'from match, thin, or density', which hints at the upstream discovery flow, and 'stubs are free' hints at a preview path. There is no explicit statement of when to prefer this over answer, ask, research, or survey, and no statement of when not to call it.

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