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

The description goes far beyond the annotations: it discloses soft-fail behavior (USPTO sunset), expected empty sections, the meaning of sources_used/sources_failed, name-resolution behavior, and the resolved:false path for private companies. It also explains why fda_products may be empty, preventing false bug reports. No contradiction with readOnly/idempotent/openWorld hints.

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 long but dense with essential details and front-loaded with example queries and the key 'ONE parallel call' concept. It is structured as one large paragraph with semicolon-separated clauses, which is readable for a complex tool, but line breaks or bullet-like separation for the many return fields would improve 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?

With no output schema, the description carries the full burden of explaining the return shape, and it does so thoroughly: it lists every section (cik, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI) and explains failure semantics. It also covers parameter semantics, input resolution, and expected empty-data cases, leaving little ambiguity for an agent invoking or interpreting results.

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% for both params, so the baseline is 3. The description adds meaning by showing the accepted value shapes with concrete examples, emphasizing that type accepts 'company' or 'ticker' interchangeably, and clarifying zero-padded CIK formatting and SEC EDGAR name resolution. This adds genuine value beyond the schema's enum and 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 leads with concrete user queries ('Tell me about X', 'research Acme') and states a precise verb+resource: full cross-source profile of a US public company in one parallel call. It clearly differentiates from siblings like resolve_entity and compare_entities by describing the comprehensive multi-source fan-out and the exact sections returned.

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 instructs 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view', giving a clear when-to-use rule. It also explains valid inputs (ticker, CIK, name) and the private-company fallback behavior, so an agent knows when this tool is appropriate and what to expect for non-match cases.

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