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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real behavioral context beyond them: every row resolves to a citable government PDF via receipt.url, and as_of guarantees no look-ahead bias. It does not discuss rate limits or result-size behavior, keeping it at a 4.

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?

Roughly five dense sentences, front-loaded with the core purpose before the filtering/pagination mechanics. Nearly every clause carries information, though the receipt.url citation instruction is a soft nudge rather than strictly necessary.

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 not be explained, yet the description still surfaces the two most important output affordances (receipt.url for citation, page.next_cursor for pagination). Combined with the 9-parameter surface fully covered, an agent has everything needed to call this 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 coverage is 100%, so a baseline of 3 applies, but the description adds meaning: chamber='executive' is where the President's disclosures live, as_of yields observed-on-or-before rows without look-ahead bias, and updated_since drives change polling. These clarify intent rather than just restating the schema, warranting a 4.

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 ('Search') and resource ('receipt-linked US government financial disclosures') and immediately scopes the corpus (both chambers under the STOCK Act plus executive-branch OGE filings). It also distinguishes itself from the sibling list_members by naming it as the resolver for member_id.

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 routing conditions: chamber='executive' for OGE/President filings, as_of for point-in-time reconstruction, updated_since for change polling, and next_cursor for pagination. It does not explicitly say when NOT to use this tool or name alternative search siblings, so it stops short of full when/when-not guidance.

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