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

Annotations already establish the safe read-only, non-open-world profile, so the bar is lower; the description goes well beyond them by disclosing the ranking algorithm, the fallback-to-sector behavior, the fund-returns-nothing case, and the fields each target carries. It stops short of auth or rate-limit context, but for a read-only lookup this is rich disclosure.

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 purpose is front-loaded in the first sentence, but that sentence is extremely long and heavily nested with parentheticals ('operating companies whose active holders overlap most, funds excluded'), making it dense to parse. Most content earns its place, but the structure could be broken up for scanability.

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 return-value burden and does so by enumerating what each target shows (13F book, peers' share, top peers, style, holder type). Combined with the fallback and fund edge cases, an agent has enough to call and interpret the tool, though the fallback trigger ('no overlap peers') could be defined more concretely.

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 all three parameters (ticker, sort, maxResults) are documented in the schema, including the sort enum values and the 1-500 clamp. The description adds no parameter-level detail beyond that, so the 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 states a specific resource (13F filers) and a precise selection rule: filers of the newest closed quarter that hold holder-overlap peers but hold no class of the stock itself. This sharply distinguishes it from siblings like GetTopHolders, GetAllHolders, and GetSuperInvestors, which describe current holders rather than non-holding prospects.

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?

Usage is implied rather than stated: the definition makes clear it is a prospecting tool (filers who do NOT yet hold the stock), and it names two edge conditions (no overlap peers falls back to sector holdings; a fund has no targets). But it never explicitly says when to prefer it over GetTopHolders or GetOwnershipSignals, nor does it state prerequisites.

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