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

Even with readOnly/openWorld/idempotent annotations, the description adds substantial behavioral context: it names the fan-out sources, explains that sources_used/sources_failed indicate real data availability, clarifies that empty sections are expected, and describes how private companies and unregistered names are handled via resolved:false. This goes well beyond the annotations.

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 and dense, but it is front-loaded with user intent examples and the key 'one parallel call' positioning. Every major chunk adds useful operational detail, though the single run-on paragraph and the repeated type/value interchangeability note create slight redundancy.

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 behavior, and it does so thoroughly: it lists returned fields, URI formats, source coverage, failure semantics, name resolution behavior, and private-company handling. An agent has enough context to invoke and interpret the tool 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 100% of the parameter semantics, including ticker/CIK/name examples and the interchangeable behavior of 'company' and 'ticker'. The description largely restates this rather than adding new parameter-level meaning; the resolved_from/resolved_to detail is more about output behavior than input semantics.

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 that this tool produces a full cross-source profile of a US public company in one parallel call, with concrete trigger examples like 'Tell me about X' and 'brief me on Tesla'. It stops short of explicitly distinguishing itself from sibling tools such as resolve_entity or compare_entities, though the 'holistic profile' framing makes the purpose clear.

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 says to 'ALWAYS PREFER' this tool over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view, which gives clear when-to-use guidance. It does not explicitly describe when-not-to-use scenarios or direct users to a specific sibling alternative for narrower lookups.

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