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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed-world scope, so the safety profile is covered. The description adds genuine value by disclosing provenance (STOCK Act reports, one filing per trade), but says nothing about data freshness, update cadence, or what a record looks like.

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?

A single front-loaded sentence with zero filler; the source and the per-trade filing linkage both earn their place. Nothing is repeated from structured fields.

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?

For a one-parameter read tool with rich annotations this is close to sufficient, but with no output schema the description should hint at the shape of a returned trade (ticker, amount, date, filer) or how results are ordered and paged. 'Most recent' only appears in the schema, not the description.

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 single 'limit' parameter is fully documented in the schema, including its default of 25 and max of 100. The description adds no parameter detail beyond that, so the schema-only 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?

The description names a specific resource — disclosed AI-stock trades from the Pelosi tracker, sourced from STOCK Act filings — which is far more specific than 'get trades'. It is distinguishable from siblings like get_investor or get_ticker, though it never explicitly contrasts itself with them or with search_stocks.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. Usage is only implied by the phrase 'AI-stock trades from the Pelosi tracker', which lets an agent infer this is a themed list endpoint rather than a per-investor or per-ticker lookup.

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