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

With no annotations, the description carries the full burden and covers cost ($0.05 per call), payment mechanisms (x402 or subscriber API key), data provenance (public disclosure, no vendor licensing), and a disclaimer (educational, not financial advice). It does not disclose rate limits or response format, but the essential behavioral traits are present.

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 front-loads the core purpose and cost before diving into payment details and examples. Every sentence adds distinct information, but the overall length is substantial. It is efficient yet dense.

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 simple 2-parameter, no-output-schema tool with no annotations, the description covers the data fields returned, gives a full example, explains the optional filter, and details payment/auth. Missing limit semantics and response structure are small gaps; otherwise the tool is well specified.

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 0%, so the description must compensate. It explains the symbol parameter ('Optional ?symbol= filter') with a concrete example, but says nothing about the limit parameter's behavior beyond the schema's default. Partial compensation for a low-coverage 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?

Description states the exact resource: 'latest US congressional stock trades (STOCK Act): member, party, buy/sell, ticker, amount, dates.' The concrete example (R-TX member, Purchase NVDA, $15,001-$50,000) makes the tool's function unmistakable. It distinguishes itself from sibling market-data tools by focusing on congressional trades.

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 implies usage context ('Per-call alternative to $25-75/mo congressional-data subscriptions') and points users to get_catalog to browse all tools. However, it does not explicitly state when to choose this over sibling tools or when not to use it. The usage guidance is implied rather than explicit.

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