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

Beyond the readOnly/idempotent annotations, the description discloses per-section behavior: patents soft-fail due to a USPTO sunset, an empty fda_products section is expected for non-biologic companies, empty sections are real no-data rather than bugs, and sources_used/sources_failed report provenance. This is exactly the kind of failure-mode and edge-case transparency agents need.

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 the tool is genuinely multi-source and the length is mostly earned through concrete return-field and failure-mode details. It is front-loaded with example queries and the core purpose before enumerating sources, though the dense semicolon-list style could be improved with short section breaks.

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: it enumerates every returned section (filings, fundamentals, patents, contracts, FDA products, hiring, news, LEI) and adds source-failure semantics. It also covers the important resolving behavior for private companies, so an agent has enough context to invoke and interpret the call 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?

The input schema already covers the two parameters and their allowed value shapes at 100% coverage, so only a small premium is earned here. The description adds useful context by noting case examples, that type is interchangeable, and that name inputs resolve via SEC EDGAR with resolved_from/resolved_to behavior, which goes slightly beyond the schema.

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 and then states a precise verb + object: "full cross-source profile of a US public company in ONE parallel call." It names the main alternatives it replaces (chained single-pack SEC/XBRL/news lookups) and clarifies it is for holistic profiles, distinguishing it from the many research siblings.

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 instructs to "ALWAYS PREFER" this tool over chaining single-pack lookups when the user wants a holistic view, and it notes the exception behavior for private companies (resolved:false with notes) so the agent knows when the tool has done its job. This is actionable when/when-not guidance rather than a vague invitation to use it.

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