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

With no annotations provided, the description carries the behavioral disclosure burden. It covers pricing, payment settlement via x402, subscriber API key options, and the educational/non-financial-advice nature of the data. It lacks explicit statements about data freshness or error behavior, but the key operational traits are disclosed.

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 core function is front-loaded in the first sentence, but the description becomes lengthy with pricing, payment instructions, marketing comparisons, and a pointer to get_catalog. Most content earns its place for a paid API, but it could be tightened without losing essential guidance.

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?

For a two-parameter tool with no output schema, the description is reasonably complete: it lists the return data fields, optional symbol filtering, payment/auth requirements, and the educational caveat. It does not explain the limit parameter's behavior or pagination, but the core use case and access details are well covered.

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 0%, so the description must compensate. It explains the symbol parameter as an optional filter, but the limit parameter is entirely unmentioned. Since limit has a default of 25 and is otherwise self-explanatory, the description still provides partial value, but fails to fully document all parameters.

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 clearly states the tool's function: retrieving recent US congressional stock transactions with specific data fields (member, party, state, buy/sell, ticker, amount range, dates). It also differentiates itself from the many sibling get_* tools by focusing on congressional trades and offering an optional symbol filter.

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 provides clear context for when to use the tool (getting congressional trades, as a per-call alternative to subscription data plans) and how to access it (x402 payment or API key). It does not explicitly list exclusions or name sibling alternatives, so it stops short of full when-not-to-use guidance.

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