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

Annotations already mark this as read-only, idempotent, and non-destructive, but the description adds substantial operational context: parallel fan-out across sources, sources_used/sources_failed semantics, empty sections meaning real 'no data', private-company resolution behavior, and the product scope limitation to biologics.

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 front-loaded with use-case examples and an explicit ALWAYS PREFER directive, and the long source/return inventory is dense but relevant. It is lengthy and somewhat repetitive with the schema's type explanation, but each major section earns its place.

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 must explain return behavior on its own—and it does thoroughly. It enumerates returned fields, source-specific content, sources_used/sources_failed, file URIs, and failure/edge-case semantics for private companies and unsupported product types.

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 adds value beyond the schema by clarifying that 'company' and 'ticker' are interchangeable and by elaborating the accepted value shapes: ticker, zero-padded CIK, or company name, including EDGAR name-resolution behavior.

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 trigger phrases and states that this produces a 'full cross-source profile of a US public company in ONE parallel call.' The verb, resource, and scope are clear, and the explicit contrast with chaining single-pack lookups distinguishes it from related 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?

The description explicitly says to prefer this tool over chaining separate SEC/XBRL/news lookups when the user wants a holistic company view. It also gives clear input guidance and specifies what happens for private companies, making selection criteria unambiguous.

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