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

Annotations already mark the tool as read-only/idempotent, and the description adds substantial non-obvious behavior: it fans out across SEC EDGAR, XBRL, USPTO, USAspending, FDA Purple Book, DOL LCA, GDELT→GNews, and GLEIF; USPTO soft-fails after the API sunset; FDA results are limited to licensed biologics; and sources_used/sources_failed distinguish real no-data from failures.

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 description is front-loaded with purpose and query examples, and the dense length is largely justified by the tool's many sources and edge cases. It loses a point for being a single run-on paragraph with some redundancy at the end about type interchangeability, which the schema already covers.

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 full burden of explaining the return shape, and it does so thoroughly: it enumerates cik, resolved_from/resolved_to, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, and LEI, plus fallbacks, empty-section semantics, and private-company behavior. Nothing essential is missing for an agent to call this correctly.

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%, and the schema already documents that type accepts company/ticker interchangeably and that value can be a ticker, zero-padded CIK, or company name. The description restates these constraints without adding meaningful new parameter semantics beyond the schema.

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 states a specific purpose: produce a full cross-source profile of a US public company in one parallel call, and anchors it with concrete user phrasings like "Tell me about X" and "brief me on Tesla." It also distinguishes itself from chaining single-pack SEC/XBRL/news lookups, making its scope clear against similar research tools.

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 explicitly says to ALWAYS PREFER this tool over chaining single-pack lookups when the user wants a holistic view, and includes representative triggers. It also explains the private-company case (resolved:false with notes) and the expected-empty FDA section, so an agent knows when a thin result is normal rather than a failure.

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