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

Even with readOnlyHint and idempotentHint already present, the description adds rich behavioral detail: single parallel fan-out, USPTO PatentsView sunset soft-fail, GDELT-to-GNews fallback, expected empty FDA results for companies with only small-molecule drugs, and resolved:false handling for private companies. This goes well beyond the 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 long, but nearly every clause carries operational value, and it is effectively front-loaded with query examples and a high-level purpose. A few repeated examples and the extended per-source return breakdown could have been trimmed, but the structure is still navigable and purposeful.

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 fully compensates by listing the major return groups (CIK, filings, fundamentals, patents, contracts, FDA products, hiring, news, LEI), explaining source-success/failure reporting, and covering edge cases like private companies and empty FDA sections. An agent has enough context to call the tool and interpret results 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?

Although the schema already describes both parameters fully, the description meaningfully extends that guidance with concrete examples, the equivalence of ticker/CIK/name inputs, zero-padded CIK formatting advice, EDGAR name resolution, and the interchangeability of type values. This materially reduces ambiguity in selecting and supplying arguments.

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 names a specific resource and operation: building a full cross-source profile of a US public company in one parallel call. It is clearly differentiated from chaining single-pack SEC/XBRL/news lookups and is reinforced by concrete user-intent examples, making it easy for an agent to recognize when this tool applies.

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 use this tool when the user wants a holistic view and directs agents to prefer it over chaining smaller lookups. It does not, however, provide an explicit when-not list beyond the implied private-company resolution behavior, so it narrowly misses a 5.

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