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

Even though annotations already declare readOnlyHint, openWorldHint, and indempotentHint, the descriptio adds significant behavior: it fan-outs across SEC EDGAR, XBRL, USPTO, USAspending, Purple Book, DOL LCA, news, and GLEIF; it discloses soft-failures and epsectyed-empty sections; it explains name resolution and the `resolved:false` behavior for private companies; and it documents `sources_used` / `sources_failed`. No annotation contradiction.

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 descriptio is long but earned: it packs source list, output shape, edge cases, and failure semantics into a structured block with clear parenthized caveats. It is front-loaded with intent and examples, though it does partially repeat the schema's `type`/`value` explaination at the end, which adds minor redundancy.

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 it does so comprehensively: CIK, name, resolved_from/resolved_to, recent filings with URIs, fundamentals, patents, contracts, FDA products, H-1B, news, LEI, and source-success indicators. It also covers key edge cases such as private companies, empty sections, and source fallacks, making the tool safely callable in an agentic context.

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?

The input schema already covers both parameters at 100% and states that `type` accepts company/ticker interchangeably and that `value` accepts ticker, CIK, or company name. The description adds concrete examples, zero-padding guidance, the name-resolution behavior, and the private-company edge case, which enrich the parameter semantics beyond the bare 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 concrete user phrasings ('Tell me about X' / 'research Acme' / 'brief me on Tesla') and states a specific action: produce a full cross-source profile of a US public company in one parallel call. It also distingrudes itself from sibling tools like compare_entities and deep_researrch by emphasizing the holistic, single-call company profile deliverable.

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 tells an agent to ALWAYS PREFER this over chaining single-pack SEC/XBRL/news lookups when a holistic view is requested, and it provides concrete input examples and fallback behavior for private companies. It does not spell out exclusionary cases for other siblings such as compare_entities or resolve_entity, so it leaves some routing inference to the agent.

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