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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two useful pieces of behavioral context beyond that: the temporal scope (newest closed quarter vs. the prior quarter) and the data-quality caveat that cost is an estimate from quarter average prices, never a filed figure. It says nothing about auth, rate limits, or output size.

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 content is informative but delivered as one sprawling ~120-word sentence with a 14-item parenthetical list, giving the reader no structure or prioritization. It is dense rather than wasteful, but it is not front-loaded and not scannable.

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 burden of explaining return content and does so thoroughly by naming each metric block (conviction, crowding, free-float ownership, concentration, holding duration, cost/loss share, active-holder change, 13D/13G filers, overlap peers, top-weight filers). It is nearly complete for a single-ticker analytics call, missing only output shape and interpretation guidance.

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%, so ticker, maxPeers, and maxHolders are already documented with defaults and clamp ranges. The description adds only marginal meaning, e.g. 'one row per company, funds excluded' for peers and 'top-scored managers' net buying' implying what maxHolders selects. Baseline 3 is appropriate 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 resource (13F ownership signals for a stock) and enumerates the exact metrics it reports, so an agent knows this is a composite ownership-analytics tool rather than a raw holder list. It never names or distinguishes itself from close siblings like GetTopHolders, GetOwnershipSummary, GetHolderMix, or GetAllHolders, so sibling selection still requires inference.

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?

There is no when-to-use guidance, no stated alternatives, and no prerequisites. The description only lists what the tool returns; an agent gets no help deciding between this and the many other ownership tools.

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