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

Even with annotations already marking it read-only and non-destructive, the description adds substantial context: free public data, no daily-limit consumption, reporting lag of up to 45 days, historical rather than live data, default no-filter summary behavior, and returned fields including late-reporting days and official filing links.

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 dense but well front-loaded: purpose, returned data, no-filter behavior, data freshness caveat, example queries, and usage restrictions all appear in a logical order. Every sentence adds operational context rather than restating the name or schema.

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 rich annotations and an output schema, the description supplies the remaining context an agent needs: data provenance, reporting delay, default behavior, example queries, and prohibited uses. Nothing material for correct tool selection or invocation is missing.

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 the schema already documents all six parameters and their bounds. The description adds meaningful usage context by explaining what happens with no filters and by grounding the look-back window in the STOCK Act reporting delay, though it does not give parameter-specific syntax beyond the schema.

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/resource—stock trades reported by U.S. House and Senate members under the STOCK Act—and lists the returned fields, making the tool clearly distinct from corporate insider-trading siblings. It also explains the no-filter behavior and the reporting-delay context.

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 explicit use cases and exclusions: examples like 'which members traded NVDA?', 'what has Pelosi bought?', and 'congressional trades this week', plus a prohibition on credit decisions, fundraising, and solicitation. It does not explicitly name a sibling alternative for corporate insider queries, so it stops short of full when-to-use/when-not/alternatives guidance.

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