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

The readOnlyHint only covers the safety profile; the description goes well beyond it by enumerating every possible verdict value and stressing they are 'never coerced to neutral', listing the returned sub-objects, disclosing the source (SEC EDGAR 13F-HR + Form 4), stating there is no tier gate or AI metering, and noting caveats ride in tool_notes. This is unusually rich behavioral disclosure for a read-only 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?

Front-loaded with the core purpose and result shape, and nearly every clause contributes unique information (source, verdict semantics, return fields, metering). It is dense and somewhat long, but no sentence is redundant with the structured fields, so only mild trimming would be warranted.

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 available, the description carries the return-value burden and does so by enumerating the verdict enum and the institutional/insider/cluster/coverage/summary payload. Combined with the source attribution, metering, and caveat location, an agent has everything needed to call and interpret it.

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?

There is a single parameter and schema coverage is 100%, so the schema already documents the ticker argument; the description only reinforces that it takes one ticker and gives no additional syntax, format, or edge-case detail. Baseline correct when the schema does the heavy lifting.

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?

States a specific verb and resource ('Quarter-aligned institutional-confluence read for one ticker') and names the three data sources fused (13F accumulation, insider Form 4 net buying, buy-cluster confirmation). It explicitly positions itself against siblings by noting it is 'a DERIVED verdict, not raw data: no per-fund rows' and naming get_institutional_holders and ol_insider_cluster_scan as its pairs, so an agent can distinguish it from those without opening a schema.

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 'Pairs with get_institutional_holders and ol_insider_cluster_scan' line and the 'DERIVED verdict, not raw data' contrast give clear context for when to reach for this fused read over the raw-holder siblings. However, it never states an explicit when-not condition (e.g., cases where the underlying raw tools are preferable), so it stops short of full routing guidance.

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