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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint:false. The description adds substantial behavioral context: it lists all fan-out sources, explains that USPTO patents soft-fail after May 2025, clarifies that empty sections are valid 'no data' results, documents the resolved:false behavior for private companies, and exposes sources_used/sources_failed semantics. This goes well beyond the annotations and prepares the agent for unusual outcomes.

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 and dense, but nearly every clause carries information: return sections, source names, failure behavior, and input forms. It is front-loaded with user intents and the 'ALWAYS PREFER' guidance. Some structure — bullet points or section breaks — would improve scannability, but the density is justified by the tool's breadth.

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 the full burden of explaining return values, and it does so exhaustively: it names every return section (cik, recent_filings, fundamentals, patents, federal_contracts, fda_products, hiring, news, LEI, sources_used/sources_failed), explains expected empty sections, documents URI formats, and specifies behavior for private companies and interchangeable parameter types. Nothing needed to invoke this tool correctly 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 description coverage is 100%, and both parameters are richly documented in the schema itself: type explains that 'company' and 'ticker' behave identically, and value already gives examples of ticker, CIK, and company name. The description reinforces these with concrete examples ('AAPL', '0000320193', 'Moderna') but adds little beyond the schema. Baseline 3 is appropriate.

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 states a specific verb ('profile', 'brief', 'research') and a concrete resource: a US public company identified by ticker, CIK, or name. It clearly differentiates this tool from simpler SEC/XBRL/news lookups by emphasizing 'full cross-source profile in ONE parallel call.' Even without naming specific siblings, an agent can infer that this is the holistic-company-overview 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 explicitly says 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view' and gives concrete user-intent triggers ('tell me about X', 'research Acme', 'brief me on Tesla'). It even notes the private-company edge case where the tool returns resolved:false with a notes line. It does not name specific sibling alternatives like compare_entities or resolve_entity, but the guidance is otherwise clear.

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