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

Beyond the annotations (readOnly/openWorld/idempotent), the description discloses a great deal: parallel fan-out across eight named sources, the sources_used/sources_failed mechanics that make 'an empty section is a real no-data, not a bug', the GDELT→GNews fallback chain, and the resolved:false + notes behavior for private companies. It even flags that a firm with only small-molecule genesic drugs will legitimately show no FDA products. These behavioral traits materially change how an agent interprets results.

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 front-loads user intents and the core purpose before diving into source and return-structure detail, and nearly every clause earns its place given the tool's complexity. However, it runs as one dense unstructured paragraph, and the input-format section largely repeats schema content, so it is efficient but not maximally tight.

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 high-complexity tool with no output schema, the description documents the entire return payload (resolved identity with resoved_from/resolved_to, up to 5 recent_filings with URIs, LATEST-10-K fundamentals, patents, federal contracts, FDA biologies, H-1B hiring, news, LEI), every input shape, and both failure modes (sources_failed and resolved:false). Nothing an agent needs to invoke it correctly is missing.

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%: both type and value already carry full descriptions, including the interchangeable 'company'/'ticker' semantics and the accepted value shapes (ticker, zero-padded CIK, company name). The description's input discussion uses the same examples (AAPL, 0000320193, Moderna) already present in the schema, adding no new meaning, so the rubric's baseline of 3 applies.

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 opens with concrete trigger phrases ('Tell me about X', 'company profile for Microsoft', 'everything you know about $TICKER') and pins the scope precisely: 'full cross-source profile of a US public company in ONE parallel call.' This makes it readily distinguishable from siblings like deep_research (broader multi-topic research), compare_entities (side-by-side comparison), and resolve_entity (identity resolution only), as well as from single-source SEC/XBRL/news lookups.

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?

It states explicitly when to prefer this tool — 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view' — and it documents the boundary case for private companies returning resolved:false rather than a failure. However, alternatives are described behaviorally rather than named by sibling tool, so routing to compare_entities or deep_research is left to inference.

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