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

Annotations already cover read-only and open-world behavior, and the description adds real context beyond them: values are filed ranges and never exact amounts, data derives from Periodic Transaction Reports, and it requires the Congress trades tracker entitlement on the account. It doesn't mention rate limits, pagination defaults, or empty-result behavior.

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?

Purpose is front-loaded in the first sentence, and the caveats (filed ranges, no Senate, entitlement requirement) are appended as compact clauses. It is slightly long but nearly every sentence carries distinct 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?

For a tool with no output schema, the description usefully characterizes the returned data fields and the ranges-only nature of values, plus the access prerequisite. Remaining gaps are pagination/limit behavior and result-volume expectations, which are minor.

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?

With 60% schema coverage, the schema already documents the member slug format, ticker example, and days semantics. The description reinforces ticker/member/transaction-type filtering and the trailing-window notion but adds little syntax detail and says nothing about the limit parameter.

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 — trades disclosed by U.S. House members under the STOCK Act — and enumerates the returned facts (who, which security, when, value range). It is clearly distinguishable from siblings like search_insiders, get_insider_profile and get_unfiltered_purchases.

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?

Gives concrete scoping guidance: filter by ticker/member/transaction type over a trailing window, and explicitly excludes Senate reports, which prevents a common mis-selection. It does not, however, name an alternative sibling for the Senate case or say when to prefer this over insider-category tools.

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