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

The readOnlyHint annotation already covers the safety profile. The description adds useful context about the data source (STOCK Act disclosures) and that results are dated by transaction, but it does not disclose behaviors like sorting, pagination, or how the limit parameter affects results. That is acceptable given the annotation, so a moderate score applies.

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 yet information-dense: key use cases, an exclusion, and a pointer to the main arguments all fit in three short sentences. The most identifying information is front-loaded, and every sentence earns its place.

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 and readOnlyHint set, the description does not need to explain return values or safety. It covers the main scenarios, the sibling differentiation, and the core arguments. The only minor gap is incomplete parameter semantics for entity and chamber, but the overall context is sufficient for correct invocation.

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 0%, so the description carries the burden. It adds meaning for ticker, member, and limit ('Args: ticker or member; limit'), and the 'US House' phrase aligns with the house default for chamber. However, entity and chamber are left unexplained, leaving part of the parameter surface undocumented.

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 states a specific verb and resource ('US House stock-trade disclosures'), identifies the two core lookup modes (by ticker, by member), and even notes the date dimension ('dated by transaction'). It also differentiates itself from the sibling get_insider_trades explicitly, so an agent cannot confuse the two.

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 description gives concrete user-phrasing examples ('which members of Congress traded X; what did a named member buy; is Congress selling X') and an explicit negative case with the correct alternative ('Not for: company insiders → get_insider_trades'). This is exemplary routing guidance.

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