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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds that the data comes from the latest 13F filings and is limited to tracked funds, which is useful framing, but it omits the filing lag/staleness and the size of the tracked universe — material caveats for 13F data.

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?

One front-loaded sentence establishes the data source and then enumerates the views with parenthetical definitions. Every clause carries information; nothing is redundant or padded.

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 a single required parameter and no output schema, the description is nearly sufficient — it explains the input and roughly what each view yields. It still leaves the response shape and data recency unstated, which matters for a filing-based analytical 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 coverage is 100% and the enum is documented only as 'Which view to return', so the description carries the real burden — it defines what each of the five view values actually returns (consensus, crowding, mostHeld, rotation, funds). That is genuine meaning added beyond the schema, though the semantics stay terse.

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 concrete resource and scope: aggregated activity of tracked hedge funds in their latest 13F filings, broken into named views. An agent can tell this is an aggregate/summary tool rather than a per-symbol lookup. It does not explicitly differentiate itself from the sibling get_13f_holders, so it stops short of a 5.

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 through the view list — an agent can infer to pick 'crowding' for top-ten concentration or 'rotation' for sector flows — but there is no explicit statement of when to use this versus get_13f_holders or other market tools, and no prerequisites or exclusions. Guidance exists only by inference.

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