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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds valuable behavioral context: specific return fields, patent API sunset with soft-fail, GDELT→GNews fallback, and URI format for filings. This goes beyond the annotations and helps the agent predict behavior without needing to invoke the tool.

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 dense and front-loaded with example user phrasings and a clear 'ALWAYS PREFER' directive. It is longer than ideal, but every sentence provides useful operational context or return-field specifics, so it remains appropriately structured.

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?

Given there is no output schema, the description thoroughly enumerates the response components (cik, company_name, recent_filings with URI patterns, fundamentals, patents, news, LEI) and explains fallback/soft-fail behavior. All necessary context for invoking the tool is present, making it fully complete.

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 the description largely repeats the same parameter information (ticker/CIK, names not supported, company type only). The description adds example value for zero-padded CIK but does not introduce substantially new semantics beyond what the schema already provides. 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 clearly states the tool produces a full cross-source profile of a US public company in one parallel call, listing the data sources and return fields. It distinguishes itself from sibling tools by explicitly saying 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups' and referencing resolve_entity for name-based lookups.

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?

Explicit guidance: ALWAYS PREFER over chaining single-pack lookups when the user asks for a holistic view. Also instructs to use resolve_entity first if only a name is available, since names are not supported. This clearly defines when to use the tool and what to do instead.

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