Get Recent Politician Trades

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

Annotations declare readOnlyHint=true, and the description confirms it's a read operation. It adds value by detailing returned fields: 'senator info, ticker, transaction type, amount, and filing delay', which is beyond annotations.

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?

Two sentences with no fluff: first states purpose, second describes output fields and filters. Essential information is front-loaded and every sentence earns its place.

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 read-only list tool with full schema descriptions, output schema, and annotations, the description covers purpose, output fields, filters, and a use case. It could mention pagination or defaults but schema handles that.

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 descriptions exist for all 4 parameters. The description highlights 'Filter by direction (buy/sell) and lookback period' which aligns with direction and days params, but doesn't add significant extra meaning for limit and offset.

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 'Get recent STOCK Act trades across all politicians' with a specific verb and resource. It distinguishes from siblings like get_politician_transactions and get_senate_trades_by_ticker by indicating it covers all politicians and recent 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 provides clear context: 'Useful for monitoring current congressional trading activity' and mentions filters by direction and lookback period. It does not explicitly exclude alternatives but implies that for specific politicians, other tools may be better.

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