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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description adds real value on top: it discloses the return shape (one markdown section per bucket), the sort order (absolute Δ market-value desc), and the crucial caveat that Δ Value includes price movement rather than pure trading activity. That caveat materially changes interpretation of results.

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, then the return format, then the sort semantics, then the filtering hint — every sentence carries distinct information with no filler.

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?

No output schema exists, but the description compensates by explaining the return structure (markdown section per bucket), row labelling by Type, and sort order. Combined with 100% schema coverage and safety annotations, an agent has everything needed to call and interpret this tool.

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 the schema already documents bucket, maxResults, reportDate, and institutionName including the partial-resolution and snapping behavior. The description's 'Use `bucket` to filter to a single bucket' largely restates the schema, so the baseline of 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?

Names a specific verb+resource (institution quarterly position-change activity) and pins down the scope precisely: initiated/increased/reduced/exited diffs against the prior quarter. It also distinguishes itself from similar siblings such as GetInstitutionPortfolio and GetInstitutionalOwnershipHistory by specifying that this is a quarter-over-quarter diff rather than a holdings snapshot.

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?

Gives a clear intended use case ('what did this fund do this quarter?') and tells the agent how to narrow output with `bucket`. It stops short of naming an alternative tool or stating when NOT to use it (e.g., versus GetInstitutionConsensusHoldings or GetMarketWide13FActivity), so it falls short of the top band.

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