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

Annotations already declare this is read-only, idempotent, and non-destructive, and the description adds substantial behavioral context beyond that: it fans out in parallel across multiple sources, reports sources_used/sources_failed, treats empty sections as genuine 'no data' rather than bugs, resolves names via SEC EDGAR, and explains the FDA product nuance. This is rich, non-redundant disclosure that materially changes 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 is thorough but dense and unstructured, packed into a single run-on flow of examples, return fields, source notes, and edge cases. It is neither concise nor well-sectioned, though nearly every sentence provides useful information. A structured layout with bullets or short paragraphs would significantly improve scanability.

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 describing return values, and it delivers: it lists all major response sections (cik, company_name, recent_filings, fundamentals, sec, xbrl, patents, etc.), explains fallback behavior (GDELT→GNews), and clarifies expected empty results. The input handling and failure modes are also fully covered, so an agent has everything needed to call and interpret this tool correctly.

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%, so the baseline is 3. The description goes further by giving concrete examples ('AAPL', '0000320193', 'Moderna'), explaining that 'company' and 'ticker' are interchangeable, and detailing name-resolution behavior including the private-company return shape. This adds real semantic value beyond the schema's own parameter 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 opens with concrete user phrasings ('Tell me about X', 'research Acme') and immediately defines the action as 'full cross-source profile of a US public company in ONE parallel call.' It enumerates the exact inputs (ticker, CIK, company name) and the returned sections, making the tool's scope unmistakable and clearly distinct from single-pack 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?

The description explicitly states when to use the tool: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also clarifies the private-company edge case (returns resolved:false rather than failing). It does not name sibling alternatives like compare_entities or deep_research and when to prefer them, so it stops short of full exclusionary guidance.

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