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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description does add genuine behavioral value by clarifying role matching ('FDA recalls as firm', 'contracts as recipient'), but says nothing about result volume, truncation, or how ambiguous name substrings are handled.

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?

A single dense sentence with the cross-topic scope and source list front-loaded and no filler. It is efficient, though the noun-phrase fragment omits an explicit verb, leaning on the title for the action.

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 source enumeration is a reasonable stand-in for what comes back, but the description omits return shape and, critically, default behavior for a tool with zero required parameters. For an aggregating dossier across six datasets, that leaves a real gap.

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 description coverage is 100% with only two optional parameters, so the schema already explains the substring semantics and the ticker-to-legal-name resolution. The description adds no parameter detail beyond that, making the baseline 3 correct.

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 resource ('cross-topic dossier for one entity') and enumerates exactly which datasets are aggregated (SEC filings, 13F, fund holdings, FDA recalls, federal register, contracts). This distinguishes it from narrow siblings like fda_firm_dossier or patents_by_assignee, though it never explicitly names a sibling it competes with.

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?

No when-to-use guidance and no routing to alternatives such as company_profile, entity_timeline, or compare_entities, all of which overlap. With zero required parameters, the description also never explains what happens if both name and ticker are omitted or which to prefer.

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