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

Annotations already cover read-only safety, so the bar is lower, and the description clears it: it discloses that the legacy Total Shares field mixes share, put/call underlying, and principal rows, that QoQ change is like-for-like with exclusions, that values may fall back to filer values or be zero, and that non-ETF primary stocks use a provisional combined view during the filing window. That is substantial methodological 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 purpose is front-loaded in the first sentence and the following sentences each carry a distinct caveat rather than filler. It is dense and long, but the length is justified by the methodology being explained; only minor tightening is possible.

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 compensates by naming the returned fields (total reported quantity, published position value, filer count, Share Chg QoQ) and explaining their interpretation pitfalls. For a two-parameter read tool, nothing an agent needs to call and interpret it is missing.

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% with only two parameters, so the schema already documents ticker format and the maxPeriods default/clamp. The description adds no parameter-level detail beyond implying quarter granularity, 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?

Opens with a specific verb and resource: 'historical trend of aggregate reported 13F exposure for an exact stock or ETF listing across multiple quarters.' It also names the outputs (quantity, position value, filer count), which distinguishes it from sibling tools like GetTopHolders or GetInstitutionQuarterlyActivity.

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 scope ('exact stock or ETF listing', multi-quarter trend) implies when this is the right tool, and it implicitly separates itself from single-quarter/single-institution siblings. However, it never names an alternative tool or states an explicit when-not condition, leaving routing to inference.

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