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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the description's job is supplemental. It adds real value: the data source (STOCK Act disclosures), the derived fields (late-disclosure flag, performance vs. S&P 500), and a compliance framing ("Facts, not investment advice"). It omits pagination/limit behavior and the freshness or latency of disclosure data.

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 resource and scope, then the two access modes, then a short disclaimer. The long field enumeration in the parenthetical is dense but earns its place by signaling the returns; nothing is filler, though the list could be tightened.

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 a full output schema, the description needn't explain return values, and annotations carry the safety profile. What remains — source, scope, ticker vs. aggregate mode, filtering options, and the not-advice caveat — is all present, so an agent can call this correctly without further probing.

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 baseline is 3. The description clarifies the ticker-vs-no-ticker tradeoff (full history vs. latest across Congress), but that is largely duplicated by the schema text, and it never explains what the `days` window actually measures or how `limit` truncates results.

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 specific resource and origin (stock trades by members of Congress from House/Senate STOCK Act disclosures) and enumerates the returned fields, so the agent knows exactly what data it gets. It does not explicitly differentiate itself from the close sibling list_congress_holdings (holdings vs. transactions), leaving that distinction to inference.

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?

"By ticker (full history) or across Congress (latest), filter by member or chamber" gives clear context for the two main calling modes. It never states when to use a sibling instead (e.g., get_congress_member for member profiles, list_congress_holdings for portfolios) or any exclusions, so it stops short of full routing guidance.

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