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

Annotations already declare readOnly/non-destructive/closed-world, so the description is free to add semantics it does add: bands are objectively measured with stated thresholds and are 'never the firm's own description', plus the closed-quarter/measurement-timing rule. That is real behavioral context 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 entire description is one enormous run-on sentence with a huge parenthetical enumeration of every metric. It is front-loaded with the purpose, but the list-of-measurements should be structured as a list; the density hurts readability.

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 values and does so thoroughly, enumerating the bands and the metrics behind them plus the benchmark set. Only minor gaps (e.g., no ordering/pagination note beyond maxPeriods semantics) remain.

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 coverage is 100% and both parameters are documented in the schema (maxPeriods with range, institutionName with partial/CIK resolution). The description adds no parameter-specific meaning, so the baseline of 3 applies.

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 (get) and precisely scoped resource (an institutional 13F filer's portfolio style quarter by quarter) plus the exact outputs it produces: style band, turnover band, holding-horizon band and the underlying measurements. This clearly distinguishes it from siblings like GetInstitutionPortfolio, GetInstitutionQuarterlyActivity and GetInstitutionSectorAllocation.

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?

It specifies the temporal constraint ('Closed quarters only; the newest quarter is measured once its filing window closes') which guides when results are available, but it never names an alternative tool or states when-not to use this one versus the other institution tools.

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