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

Annotations already declare readOnly/openWorld/idempotent, so the description's remaining job is failure semantics—and it does this extensively: USPTO PatentsView 'sunset May 2025 — soft-fails until reactivated'; FDA sections where an empty result is 'expected, not a failure'; and `sources_used`/`sources_failed` meaning an empty section is 'a real "no data", not a bug.' It also discloses the GDELT→GNews news fallback and that a private company returns resolved:false with an explicit notes line rather than a bare error. No contradiction with annotations.

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?

Information-dense with the most decision-relevant content front-loaded: trigger examples, 'in ONE parallel call,' and the 'ALWAYS PREFER' rule precede source details and return semantics. Every sentence carries load with no filler, but the single wall-of-text format without bullets or headers makes a roughly 600-word block harder to scan than it should be.

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 return values and does so thoroughly: top-level fields (cik, company_name, resolved_from/to), recent_filings with pipeworx:// URIs, fundamentals from the latest 10-K, per-source section semantics, and the sources_used/sources_failed diagnostic. Edge cases (private companies, soft-failing USPTO, expected-empty FDA results) are covered, so an agent knows both how to invoke it and how to interpret whatever comes back.

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 baseline is 3; both `type` and `value` already carry thorough descriptions including the ticker/CIK/name formats. The description adds genuine extra meaning by clarifying that 'company' and 'ticker' are interchangeable inputs and by tying resolution outcomes (resolved_from/resolved_to, resolved:false for private companies) to the `value` parameter. This is a modest but real supplement over 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?

States a specific verb+resource: 'full cross-source profile of a US public company in ONE parallel call.' Opening query examples ('Tell me about X' / 'research Acme' / 'brief me on Tesla') anchor exact user intents, and the enumerated fan-out sources (SEC EDGAR, XBRL, USPTO, USAspending, FDA Purple Book, H-1B, news, GLEIF) distinguish it from siblings like resolve_entity and compare_entities without ambiguity.

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?

Gives an explicit directive: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' naming the alternative pattern it replaces. The trigger-phrase examples at the start make the selection condition concrete. While it does not enumerate exclusions against siblings like compare_entities or deep_research, the holistic-single-entity condition plus 'ALWAYS PREFER' is strong enough to route an agent correctly.

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