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

Annotations already establish readOnly/safe/openWorld=false, so the description's job is marginal. It earns credit for disclosing non-obvious behavior: trades priced at quarter-average prices, filers with no prior-quarter 13F contributing no flow, and the buckets being regulatory records that never name individuals.

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?

Two sentences, front-loaded with the purpose and metrics before the caveats. The second sentence is dense with an eight-item bucket list, but every clause carries information and nothing is 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?

With no output schema, the description must carry the return-value burden, and it does describe the measures produced and two important computational caveats. For a four-parameter, fully documented read tool this is largely complete, though bucket-by-sector output shape could be clearer.

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 baseline is 3. The description restates the dimension options and the sector split in prose, adding a little interpretive context (e.g. that bucket implies groupBy=sector) but no syntax or meaning beyond the schema.

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 and resource: market-wide 13F money flows by kind of filer, and enumerates the measures returned (net flow, net flow as % of prior book, net buyers vs sellers). It is clearly a market-aggregate tool rather than an institution-level one, but it never names its nearest siblings (e.g. GetMarketWide13FActivity, GetTopInstitutionalBuyersSellers), so an agent must infer the distinction.

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 description implies when the tool fits (closed-quarter flow analysis, optional sector split) and notes the 'with ETFs apart' handling, but gives no explicit when-not or alternative-tool routing. Usage is inferable rather than stated.

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