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

Annotations only declare read-only/idempotent behavior; the description adds substantial behavioral context: cross-source fan-out, each returned section, sources_used/sources_failed, empty-section semantics, private-company resolved:false behavior, and the GDELT→GNews fallback. It even warns that small-molecule drugs will show no FDA products, which is expected behavior, not failure. No contradiction with annotations.

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 and front-loaded with trigger examples and the core directive, and nearly every clause adds meaningful source or behavior detail. However, it reads as one long run-on paragraph, and some parameter information is duplicated from the schema.

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 correctly carries the burden of explaining return values. It enumerates all returned sections, their sources, how to interpret empty sections, what happens with private companies, and which source data is expected to be absent. This is complete enough for an agent to select and invoke the 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?

The input schema already provides 100% coverage with detailed descriptions of type and value, including ticker/CIK/name forms and interchangeability. The description repeats much of this and adds some output-related detail about name resolution, but it does not add significant new parameter-level meaning beyond the 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 clearly states the tool produces a full cross-source profile of a US public company, with concrete trigger examples and a specific verb+resource framing. It also distinguishes itself from single-pack SEC/XBRL/news lookups by saying it is preferred for holistic views.

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 says when to use it: when the user asks for a holistic view, research, briefing, or company profile, and ALWAYS PREFER over chaining single-pack lookups. It does not explicitly name or exclude sibling alternatives like compare_entities or deep_research, so it falls just 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.