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

With no annotations, the description carries the transparency burden. It discloses meaningful constraints: public records only, the BlindOracle trust envelope, and the $0.10 USDC per-call cost. However, it does not clarify whether the operation is strictly read-only, what the response contains, or how failures are handled.

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?

The entire description is two compact sentences plus a cost note; every element is informative and there is no filler. The source scope and trust wrapper are front-loaded.

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 tool with no output schema and only one free-text parameter, the description should specify the expected payload format (especially how the URL is expressed in the task) and what result is returned. It leaves the most important operational detail ambiguous, so despite its clarity it is not complete enough for unambiguous invocation.

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 input schema documents the single 'task' parameter as opaque query text (100% coverage), and the description adds that the task concerns a buyer-supplied public records URL, which clarifies what content belongs in the task string. This goes beyond the schema's generic label.

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 description names a specific operation (public business-registry record extraction) with explicit sources (SEC, state Secretary of State, UK Companies House) and a distinguishing mechanism (buyer-supplied URL, BlindOracle envelope). This clearly differentiates it from siblings like data.sec-edgar-filing and data.web-extract.

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 description implies the tool is for extracting registry records from a buyer-provided public URL, but it never explicitly states when to prefer it over similar tools like data.sec-edgar-filing or data.web-extract, and provides no when-not-to-use guidance. The context is helpful but largely implicit.

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