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

With readOnlyHint already present, the description adds helpful behavioral context by stating that the result is one row per transaction and includes the disclosed amount range and filing PDF. This is useful beyond the annotation because it tells the agent what kind of output and data shape to expect.

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 front-loaded with the core purpose, then lists query dimensions and the return shape in two efficient sentences. There is no fluff or unnecessary repetition.

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 simple read-only query tool with five optional parameters and no output schema, the description sufficiently covers the data source, available filters, and primary output fields. Some minor details like ordering, exact ticker matching, or empty-result behavior are absent, but they are not critical given the schema coverage.

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?

All five parameters are individually documented in the schema, so the baseline is 3. The description adds a coherent framing of the filters ('by member name, ticker, transaction type or date') but does not materially enrich parameter semantics 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?

The description clearly identifies the tool as returning congressional stock trades from House and Senate Periodic Transaction Reports, and lists the main query dimensions: member name, ticker, transaction type, and date. It is specific enough to be understood, though it does not explicitly differentiate itself from siblings like 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 provides clear context for when this tool is appropriate: querying disclosed congressional stock trades by several useful filters. It does not explicitly name alternatives or exclusion criteria, but the domain is well-scoped by 'members of Congress' and the filter list.

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