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

Annotations already signal readOnly/openWorld/idempotent/safe, and the description adds substantial behavioral detail beyond that: fan-out architecture, per-source soft-fail behavior, resolved_from/resolved_to semantics, source-level success/failure reporting, and the explicit warning that empty sections are real 'no data' not bugs. The GDELT→GNews fallback and USPTO sunset behavior further clarify nondeterministic or degraded outcomes.

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 dense but appropriately so for a multi-source aggregator; the key directive and examples are front-loaded, and each later clause maps to a specific output section or edge case. The long semicolon-heavy sentence is slightly hard to scan, but there is little dead weight.

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 thoroughly: cik, company_name, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI, sources_used/sources_failed, and the private-company response shape. It even explains expected empty results and soft-fail behavior, leaving an agent well prepared to interpret the response 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?

The schema already documents the two parameters and their accepted shapes, so baseline is 3. The description adds meaning by explaining that 'type' values 'company' and 'ticker' are interchangeable and that name resolution now works via SEC EDGAR's company-name match, plus how private companies are handled. This goes beyond the schema without being redundant.

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 and states a specific deliverable: 'full cross-source profile of a US public company in ONE parallel call.' It names the fan-out sources and the returned sections, so an agent can clearly distinguish this holistic profile tool from narrower lookups. The use of 'ALWAYS PREFER' sharpens the purpose further.

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 says when to use this tool: any holistic 'tell me about X' request, and to prefer it over chaining single-pack SEC/XBRL/news lookups. It also covers acceptable inputs (ticker, CIK, name) and what happens for private companies, including a non-failure 'resolved:false' path. This is actionable usage guidance that prevents both under-use and misuse.

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