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

The description goes well beyond the readOnly/openWorld/idempotent annotations by disclosing soft-failure behavior (USPTO sunset), expected empty sections for fda_products, the meaning of sources_used/sources_failed, and company-name resolution behavior. This is exactly the kind of context an agent needs to interpret results correctly.

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 front-loaded with user intents and the routing directive, and it is well organized for a complex multi-source tool. However, the initial source list ("fans out across SEC EDGAR, XBRL, USPTO patents...") is redundant with the subsequent detailed section-by-section breakdown, adding length without new information.

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 responsibility of explaining what the agent will receive; it enumerates every return section, the URIs used, failure semantics, and the resolved/unresolved distinction. It also covers all input forms and edge cases, so an agent can invoke it correctly and interpret results without further assumptions.

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 documents both parameters fully with examples, so the baseline is 3. The description adds value by clarifying that "company" and "ticker" are interchangeable, that values can be a ticker, zero-padded CIK, or name, and by explaining name resolution via SEC EDGAR. This is helpful but somewhat overlaps with schema content.

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 intents ("Tell me about X", "research Acme", "brief me on Tesla") and states the deliverable: a full cross-source profile of a US public company in one parallel call. It clearly distinguishes itself from chaining single-pack lookups, which is the main alternative an agent might consider.

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?

It explicitly says to ALWAYS PREFER this tool over chaining single-pack SEC/XBRL/news lookups when a holistic view is requested, and gives example phrasings that trigger it. It also covers when not to expect a profile: private companies return resolved:false with a notes line rather than a failure.

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