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 cost ($0.01/call in USDC on Base, eip155:8453) and the exact payment mechanism (x402 via params._meta["x402/payment"]) plus the HTTP endpoint, which is genuinely useful. But it says nothing about failure behavior for unknown companies, partial source failures, latency, or result structure for a tool that fans out across five-plus data sources.

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 capability list is front-loaded and useful, but pricing is stated twice ('$0.01 per call in USDC on Base' and again in the 'Price:' sentence) and 'Free previews available' is left dangling without explanation. Roughly a third of the text is redundant.

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 one-parameter aggregation tool with no output schema and no annotations, the description conveys the sources queried and the cost/payment model, which is adequate. It is still incomplete on two things an agent needs: how the combined multi-source result is shaped, and what happens when one source (e.g., sanctions or RDAP) has no match.

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 description coverage is 100% and there is a single required parameter whose example ('Apple Inc' or 'AAPL') is already in the schema. The description adds no additional meaning about resolution rules, ambiguity handling, or whether ticker vs. name changes the output, so it sits at or below the baseline of 3.

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 the specific resource bundle (SEC EDGAR identity/filings, full-text search, OFAC SDN + EU sanctions, RDAP, DNS) and states it returns them 'in one call', which is a concrete verb+resource statement. It does not, however, distinguish this batch tool from clearly related siblings such as company_facts__risk or company_facts__dossier_batch, so the agent must infer the difference from the name.

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 when-to-use or when-not-to-use guidance and no named alternative, despite several overlapping siblings (risk, dossier_batch, lookup_batch, seller_screen). 'Free previews available' gives a hint about trial use but does not explain conditions for choosing this tool over the single-company or dossier variants.

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