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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds one useful behavioral fact beyond that – results are normalized across two heterogeneous House and Senate sources – but says nothing about pagination, rate limits, or the chamber-specific quirks that actually govern behavior here.

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; every clause (public filings, both chambers, normalized rows) carries information. Nothing to trim.

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?

An output schema exists, so return values need no explanation, and the schema fully documents parameters. However, for a 17-parameter tool with heavy chamber-specific rules and cross-parameter constraints, the description is thin – it does not flag any of the House/Senate behavioral splits that an agent must know to call it correctly.

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 100% and each of the 17 parameters is documented in the schema (including enum-like allowed values for sort and chamber). The description adds no parameter meaning beyond that, so the baseline 3 is correct.

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 gives a specific verb and resource ('Searches public congressional stock-disclosure filings') and adds scope detail (both House and Senate sources, normalized rows). It is clear on its own, but it never names or differentiates itself from the close sibling congress_report, so it falls short of a 5.

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 when-to-use, when-not-to-use, or alternative guidance. Given a sibling (congress_report) that plausibly overlaps, an agent gets no help deciding between them; only the implicit 'it's a search' context is available.

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