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

Even with readOnlyHint and idempotentHint already set, the description adds substantial behavioral detail: it fans out across SEC, XBRL, USPTO, USAspending, FDA, DOL, GDELT→GNews, and GLEIF; notes that USPTO PatentsView is sunset and soft-fails; explains that empty sections mean 'no data,' not bugs; and states private companies return resolved:false with an explicit notes line. This fully manages agent expectations beyond 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 dense, and nearly every sentence carries a distinct piece of information: input forms, source fan-out, field semantics, failure behavior, and fallbacks. It would benefit from bullet formatting for readability, but it is not padded; the length is justified by the tool's complexity.

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 bears the full burden of explaining what is returned. It lists all returned fields (cik, company_name, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI, sources_used/failed), explains soft-fail conditions, and gives expected empty-section semantics. An agent has enough context to invoke the tool and interpret results.

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 schema already covers both parameters (100% coverage), so baseline is 3. The description adds meaningful clarification: type values are accepted interchangeably, value may be a ticker, CIK, or company name, and name resolution happens via SEC EDGAR company-name match. This reduces ambiguity beyond the schema itself.

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') and then states the core action: 'full cross-source profile of a US public company in ONE parallel call.' It clearly identifies the resource (US public company) and differentiates the tool from single-source SEC/XBRL/news lookups, so an agent can recognize when this is the right high-level profile tool.

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 gives an explicit usage rule: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also clarifies valid inputs and the private-company fallback. However, it does not name or exclude related sibling tools like compare_entities or resolve_entity, so the when-not-to-use guidance is incomplete.

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