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

With no annotations, the description carries the full behavioral burden; it does disclose two genuinely useful traits — the consult is 'Paid' and the return is a JSON envelope whose fields it enumerates — which covers the output shape in the absence of an output schema. It stops short of explaining the payment mechanism (x402), what happens on non-payment, latency, or failure modes, which matters given the sibling oracle_diagnose_402 exists.

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?

Two short, front-loaded sentences with no filler; the paid nature and the response envelope come first. Density of unexplained jargon ('x402/MCP/A2A/Bazaar') costs it a point, since those tokens do not earn their place without context.

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 payment-gated tool with no annotations, no output schema, and undocumented parameters, the description partially compensates by listing the envelope fields, which removes the need to explain return values. It leaves the more consequential gaps — how payment is required/handled and what the optional audience parameter does — unaddressed.

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?

Two parameters with 0% schema coverage and no descriptions in the schema, so the description must compensate — and it does not. Neither 'question' nor the optional 'audience' is mentioned, leaving the agent to infer the meaning and any expected format (length, language, audience values) entirely on its own.

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 action (consult) on an 'oracle' resource and names the protocol surfaces it bridges (x402/MCP/A2A/Bazaar), but 'consult' is vague about what actually happens and it never differentiates itself from siblings like oracle_review_mcp or oracle_diagnose_402. An agent can guess it submits a question for a paid answer, but the framing is jargon-heavy.

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, when-not-to-use, or pointer to any sibling alternative, even though several siblings (oracle_review_mcp, oracle_bazaar_rewrite, oracle_diagnose_402) look closely related. The only implied guidance is the word 'consult'.

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