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

readOnlyHint already covers the safety profile, yet the description adds genuinely useful behavior: a hard 20-row cap per call on every customer key, newest-first ordering, and cursor-based pagination. It does not describe what a row contains, but for an annotated read tool this is solid extra context.

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, zero filler, with the resource scope front-loaded and pagination behavior immediately after. Every clause carries information.

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 covers ordering, row cap, disclosure linkage and pagination, which is most of what an agent needs. It stops short of describing the row fields (ticker, politician, date, size), a minor gap for a read-only list 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% so the baseline is 3, but the description adds meaning the schema lacks: the 20-row ceiling effectively caps the limit parameter regardless of key, and it explains that cursor comes from a prior call's next_cursor. That goes beyond the one-line schema descriptions.

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?

Specific verb+resource: it lists disclosed House and Senate trades, states the ordering (newest first) and the disclosure linkage. An agent can distinguish it from the sibling list_insider_trades without opening either schema.

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 gives concrete operating guidance (up to 20 rows per call, page with next_cursor) but never states when to choose this tool over list_insider_trades or the other list_* siblings, and imposes no exclusions. Usage is implied by the resource name rather than explained.

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