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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a useful disclaimer ('Facts, not investment advice') but omits material behavior: how stale disclosure data is, whether a name search can return multiple members, and what days/limit default to.

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?

One compact sentence block that front-loads the resource and its contents; the trailing disclaimer is short and intentional. No 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 does not need to specify return shape and correctly focuses on scope plus identification. The remaining gap is lookup ambiguity and data freshness, which matter for a disclosures tool but are minor against the annotations.

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 all four parameters are already documented. The description only restates the name-or-id choice, adding no semantics for days, limit, or precedence when both id and member are supplied.

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 concrete resource (a single member of Congress) and enumerates the payload: party, chamber, state, net worth, trades, holdings. This distinguishes it from list-style siblings such as list_congress_trades, though it never names those siblings explicitly.

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?

'Find them by name or id' gives lookup guidance but says nothing about when to choose this profile tool over list_congress_trades, list_congress_holdings, or get_whale_trades, nor what to do on ambiguous name matches.

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