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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context about the data source and scoping rules, but it does not disclose return format, pagination, or how limit interacts with the results. That is a moderate gap, but the read-only annotation lowers the burden.

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?

The description is compact and well-structured, with clear section labels for HOUSE and SENATE. Every sentence adds information about how to use the tool, and the most important scoping rule (chamber) is front-loaded.

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?

The tool has 5 optional parameters and an output schema, and the description covers the main usage axes and source distinctions. It does not explain the limit parameter or what the output contains, but the output schema exists and the core selection logic is fully described. A small gap remains around limit and result ordering.

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 0%, so the description carries the full burden of explaining parameters. It explains chamber, ticker, entity, and member with usage context, but it does not explain the limit parameter or the exact relationship between entity and ticker. Still, it adds substantial meaning beyond the bare 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?

The description clearly states the tool returns congressional stock-trade disclosures under the STOCK Act, and distinguishes the house vs senate sources. It names the specific axes (ticker/entity/member) and the data source (House Clerk's bulk export), so an agent can tell it apart from sibling tools like get_insider_trades.

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 explicitly explains when to use each parameter axis: chamber selects house or senate, house supports ticker/entity or member, senate is ticker-scoped. It also states defaults and the source of the data, giving clear context for selecting this tool over alternatives.

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