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

Annotations already mark this as read-only, idempotent, and non-destructive, so the bar is lower, but the description adds substantial behavioral context: source fan-out, GDELT→GNews fallback, USPTO patent API soft-fail, expected-empty FDA results, sources_used/sources_failed semantics, and resolved:false behavior for private companies. No contradiction with annotations exists.

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 densely packed and front-loaded with purpose and usage, but it is a single unwieldy paragraph with many semicolon-separated details and a long list of trigger examples. It repeats some parameter semantics already present in the schema, and it would be easier for an agent to parse with bulleted structure, so it is not concise despite being informative.

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?

Even though there is no output schema, the description fully enumerates the return sections (cik, company_name, recent_filings, fundamentals, sources_used/sources_failed) and explains edge cases such as resolved:false for private companies and expected-empty sections. Given the tool's high complexity and lack of output schema, this is remarkably complete for safe and correct invocation and result interpretation.

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 documents both parameters fully, including accepted shapes, so the baseline is 3. The description adds above-and-beyond value by giving concrete examples ('AAPL', '0000320193', 'Moderna'), clarifying that type is interchangeable, and explaining what happens for names that resolve or fail ('resolved_from/resolved_to', 'resolved:false'), which helps the agent interpret the value parameter correctly.

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 trigger phrases and states the core function: 'full cross-source profile of a US public company in ONE parallel call.' It clearly identifies the resource (US public company) and the action (profile/brief/research), and it distinguishes itself from single-source SEC/XBRL/news lookups, so an agent can tell it apart from narrower tools.

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 gives explicit when-to-use guidance ('ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view') and provides many trigger examples. It also covers the private-company edge case, but it does not explicitly say 'do not use when X' or name a specific sibling tool like compare_entities or resolve_entity as the alternative.

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