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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint, and the description adds substantial behavior beyond that: empty sections are a real 'no data' not a bug via sources_used/sources_failed, FDA products legitimately empty for small-molecule companies, USPTO PatentsView AP sunset soft-fails until reactivated, resolved:false + notes line for private companies, and GDELT→GNews fallback. This is exactly the context annotations cannot 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?

High information density — nearly every clause carries operational value (source fan-out, no-data semantics, input shapes, resolution behavior), and trigger phrases are front-loaded ahead of mechanics. It is, however, a long unbroken block with semicolon-separated clauses and some redundancy with schema text (type interchangeability, input forms), so it is not perfectly structured.

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?

This is a complex fan-out tool with no output schema, so the description must carry return-value and failure semantics — and it does: cik/company_name/resolved_from/resolved_to, recent_filings with pipeworx:// URIs, LATEST 10-K fundamentals fields, per-source expectations, and explicit empty-section semantics. 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 coverage is 100% — both `type` and `value` already document enum semantics, interchangeability, ticker/CIK/name forms, and SEC EDGAR name resolution. The description largely restates the same input forms ('Pass a ticker, zero-padded CIK, OR a company name' and type interchangeability) rather than adding new meaning, so the baseline 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?

States a specific verb+resource+scope: 'full cross-source profile of a US public company in ONE parallel call,' with concrete trigger phrases ('Tell me about X', 'brief me on Tesla', 'company profile for Microsoft'). Distinguishes itself by explicitly saying to prefer it over chaining single-pack SEC/XBRL/news lookups, so an agent can tell it apart from narrow lookup tools.

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?

Provides explicit trigger examples and a clear preference rule ('ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view'), which tells the agent when this tool is the right choice. It does not name sibling tools like compare_entities or resolve_entity as alternatives, nor state when NOT to use it, so it falls short of a 5.

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