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

Annotations already supply readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it explains a single company can be resolved from a name via SEC EDGAR, that private companies return resolved:false with a notes line rather than a bare failure, and that empty sections are real 'no data' states, not bugs. It doesn't mention rate limits, but the parallel fan-out behavior and fallback chain are clearly disclosed.

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 information-rich, front-loading example queries and the primary preference rule. However, it becomes a long run-on paragraph with heavy parenthetical asides and a somewhat convoluted typo-heavy joke about patents and FDA products. Every section is informative, but the structure sacrifices readability; a few bullet points or shorter sentences would make it easier for an agent to parse.

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?

For a complex tool with two simple parameters and no output schema, the description thoroughly covers input resolution, expected source fan-out, return sections, empty-data semantics, and private-company behavior. It lacks an explicit note on rate limits or timeouts, but the description is otherwise comprehensive enough for an agent to invoke the tool correctly and interpret results accurately.

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 coverage is 100%, so both parameters are already documented in the input schema. The description reinforces the accepted value shapes (ticker, CIK, name) and notes that `type` values are interchangeable, adding slight clarity about the 'both behave identically' nuance. It does not meaningfully go beyond the schema's documentation, so 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 opens with concrete example queries and states the exact resource: a full cross-source profile of a US public company in one parallel call. It distinguishes itself from sibling tools by explicitly saying ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when a holistic view is requested.

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 tells the agent when to use it (user asks for a holistic view, 'tell me about X', 'research Acme') and when not to (it should not chain single-pack lookups). It also specifies accepted input shapes and the behavior for private companies, so an agent can decide between this and siblings like resolve_entity or compare_entities.

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