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

Annotations already mark the tool read-only and non-destructive, and the description adds substantial behavioral detail: parallel fan-out across sources, sources_used/sources_failed semantics, empty sections meaning real 'no data', name resolution behavior, and expected absence of small-molecule drug data. This goes well beyond what annotations or schema provide.

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 a dense, unstructured paragraph with redundant input examples and noisy parentheticals such as 'sorted?' and 'up to N, ...' that read as unfinished. The key usage rule appears only after a long query-example list. The detail is valuable, but the lack of structure and repetition hurt scannability.

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?

There is no output schema, and the description compensates by enumerating every return section, including cik, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, and LEI. It also explains failure semantics, empty sections, and private-company behavior. For a complex multi-source tool, this is highly complete.

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%, so the baseline is 3. The description reinforces that type and value shapes are interchangeable and gives concrete examples, but it does not introduce significant new parameter semantics beyond the schema's already thorough enum and property descriptions.

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 clearly defines the tool as a full cross-source profile of a US public company in one parallel call, with explicit example queries. It distinguishes itself from chained single-pack SEC/XBRL/news lookups, which is the main alternative an agent might otherwise select.

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 prefer this tool over chaining single-source lookups when the user asks for a holistic company view. It also explains accepted input forms and how private companies are handled. It does not exhaustively contrast with all sibling tools like resolve_entity or compare_entities, but it gives sufficient decision context.

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