Congressional Trades by Stock

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

The readOnlyHint annotation already establishes that this is a safe read. The description adds genuinely useful behavioral context beyond that: results are newest-first, the default window is one year, and amounts are disclosed ranges rather than exact values. Minor gap: nothing about pagination/offset interplay or response size limits.

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?

Three sentences, all earning their place: scope, then return-shape caveats, then the alternative-tool routing. Front-loaded with the ticker scope so the agent gets the critical selector first.

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 no output schema, the description usefully characterizes the returned fields (members, purchase/sale, transaction and filing dates, disclosed amount ranges, Asset instrument type), which the agent would otherwise have to guess. Slightly light on pagination behavior for a tool with an offset parameter, but otherwise complete.

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 every parameter (offset, ticker, startDate, endDate, maxResults, transactionType) is already documented in the schema itself. The description only re-states the newest-first ordering and the one-year default, adding no syntax or semantic detail beyond the structured fields.

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 verb (Get) and resource (congressional securities transactions) scoped to a ticker, which immediately distinguishes it from the member-centric sibling. The ticker scope is baked into the first clause so an agent can route without opening the 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?

Explicitly names the alternative tool and the condition that selects it: 'Use GetMemberTrades for one member's transactions across all tickers.' Combined with the ticker-scoped purpose, the when-to-use decision is fully determined.

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