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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint, and the description adds substantial beyond-annotation behavior: parallel fan-out across sources, the sources_used/sources_failed contract, the expectation that generic/small-molecule drug companies legitimately show no FDA products ('that is expected, not a failure'), and name-resolution semantics producing resolved_from/resolved_to. Nothing contradicts the annotations — the described behavior is consistent with read-only, idempotent, open-world.

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 long, but nearly every sentence earns its place given the tool's complexity: examples, source fan-out, return fields, and edge-case caveats. Minor deduction for a dense single-paragraph wall of text that would benefit from structuring, and for some redundancy with the schema where input formats and type semantics are repeated.

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 full burden for return values — and it delivers exhaustively: cik, company_name, resolved fields, recent_filings with pipeworx URIs, fundamentals scoped to LATEST 10-K, each source section, the sources_used/sources_failed error contract, and edge-case behavior for private companies and drug-type companies. Nothing an agent needs to invoke or interpret the result is missing.

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 baseline is 3. The description goes further: it asserts type/value interchangeability explicitly, documents the zero-padded CIK convention with an example ('0000320193'), and explains that passing a name triggers SEC EDGAR company-name resolution with resolved_from/resolved_to in the output — tying parameter choice to observable 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 user phrasings ('Tell me about X', 'research Acme', 'brief me on Tesla') and states a specific verb+resource+scope: 'full cross-source profile of a US public company in ONE parallel call'. It enumerates the exact sources fanned out (SEC EDGAR, XBRL, USPTO, USAspending, Purple Book, DOL LCA, GDELT→GNews, GLEIF) and return sections, making it unmistakable and clearly different from siblings like resolve_entity or compare_entities.

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?

Contains an explicit routing rule: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' Exclusions are also stated: it targets US public companies, notes 'person/place coming soon' as out of scope, and explains private companies return resolved:false with a notes line — signaling this tool is not the fit for them.

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