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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds value beyond that by enumerating the returned data (lobbying amounts, trades, latest action, official link) and by flagging that links are correlational, not evidence of motive. It stops short of noting pagination or how limit interacts with result volume.

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?

Three tight sentences with the payload described first and the search axes second; nearly every clause carries information. The leading phrase 'Bills in Congress linked to money' duplicates the title, a small redundancy, but overall it is well front-loaded and free of filler.

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?

With an output schema present, the description needn't enumerate return fields, yet it does describe the payload shape; annotations cover the safety profile. What's missing for a fully complete picture is combination/filter semantics and result-set behavior (limit, pagination), which matters for an open-world search tool.

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%, so all four parameters are documented in the schema itself; the description merely restates the search axes (ticker, member, bill title/number). It adds no new semantics such as whether multiple filters are ANDed or how the string-typed limit behaves, so baseline 3 applies.

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 names a specific resource and a specific join: bills in Congress plus the companies that lobbied on each bill (with amounts) plus trades by members in those companies' stocks, plus latest action and official link. This is clearly distinguishable from siblings like list_congress_trades (trades only) or list_corporate_lobbying (lobbying only), so an agent knows this is the cross-linked view.

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?

It gives concrete entry points ('Search by ticker, member or bill title/number') and an epistemic caveat ('For research, not proof of motive'), which implies usage. But it never says when to prefer this over list_congress_trades, list_congress_holdings, or list_corporate_lobbying, nor does it state exclusions or prerequisites.

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