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

Annotations already cover the read-only/idempotent safety profile, so the description's job was to add behavioral depth — and it does abundantly: parallel fan-out across sources, the `sources_used`/`sources_failed` mechanism with the explicit reassurance that an empty section is 'a real "no data", not a bug', resolved:false with a notes line for private companies, and the FDA nuance that small-molecule-only companies will legitimately show zero products. These disclosures prevent serious misinterpretation of 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 content is front-loaded and information-dense, but it is one long unbroken paragraph with seven near-duplicate example phrasings in the opener, and it contains garbled artifacts ('sorted with negative?', a mangled/duplicated patents section). Every sentence carries value, but the structure is not appropriately sized or scannable for an agent.

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 must explain return values — and it does, enumerating each return field (cik, resolved_from/resolved_to, recent_filings with URIs, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI) plus the sources_used/sources_failed contract. It loses a point only because the garbled patents/return-field fragment undermines part of that enumeration.

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 mostly restates the schema ('type accepts company or ticker interchangeably — both take the same value shapes') with added concrete examples ("AAPL", "0000320193", "Moderna") and the name-resolution behavior. Useful but largely redundant with 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 opens with seven concrete user phrasings and then states the core purpose precisely: 'full cross-source profile of a US public company in ONE parallel call.' This is a specific verb+resource+scope that clearly distinguishes it from siblings like resolve_entity, compare_entities, and deep_research — an agent can tell what it does without opening the schema.

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 explicitly states when to use it ('when the user asks for a holistic view') and what to avoid instead ('ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups'). It also gives input-routing guidance — ticker, CIK, or name; and the private-company fallback behavior. This is explicit, actionable selection guidance.

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