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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds useful source context ('from periodic transaction reports') and mentions included fields like dates, lag, dollar ranges, and sources, but does not disclose pagination, result limits, or how the openWorldHint affects completeness.

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, front-loaded with the core action and resource, and contains no filler. The second sentence adds useful output context, though it could have been used to clarify parameter behavior instead of listing generic result attributes.

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 8 optional parameters and no output schema, the description is not complete enough for an agent to predict how filters combine or what the response structure looks like. It conveys the data categories but omits filtering behavior, result shape, and relationship to the sibling Senate 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 only 13%, with only 'ticker' having its own description. The tool description mentions 'ticker and member summaries' but does not explain the semantics of side, year, limit, owner, member, assetType, or minAmount. It therefore fails to compensate for the low schema coverage.

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 uses a specific verb ('Get') and names a concrete resource ('House member transactions') plus several specific data categories (ticker and member summaries, stock returns, party, committees). It distinguishes itself from the sibling 'congress.senate_trades' by explicitly targeting House disclosures.

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 usage context is implied by the word 'House' and the sibling congress.senate_trades, which suggests this tool is for House rather than Senate data. However, it never explicitly states when to use this tool versus alternatives or mentions any exclusions or prerequisites.

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