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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the regulatory provenance (STOCK Act), that dates are transaction dates rather than filing dates, and the House-only limitation. It stops short of mentioning disclosure lag or result freshness, which would be the remaining useful detail.

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?

Front-loaded with the core definition, then triggers, then exclusion, then args — no wasted sentences. The arg line listing only two of five parameters is the one weak spot, being both incomplete and slightly inaccurate.

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, return values need not be explained. Purpose, routing, and the House-only constraint are covered; only the entity/chamber parameters and any disclosure-lag caveat are left to the schema, which is a minor gap for a read-only lookup 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 the schema already documents all five parameters well (including the entity-vs-ticker distinction and chamber default). The description's 'Args: ticker or member; limit' is a partial and slightly misleading summary — it omits entity and chamber and implies the two selectors are mutually exclusive. Baseline 3 with high 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?

Specific verb+resource: 'US House stock-trade disclosures (STOCK Act) by ticker or by member, dated by transaction.' It names the data source and both access axes, and explicitly distinguishes itself from the sibling insider-trades tool, so an agent can route without opening either schema.

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 three concrete user-question triggers ('which members traded X', 'what did a named member buy', 'is Congress selling X') and an explicit negative routing rule ('Not for: company insiders → get_insider_trades'). When-to-use and when-not-to-use are both covered.

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