Get Senate Trades by Ticker

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

Annotations already provide readOnlyHint=true, so the description adds value by specifying it returns 'recent STOCK Act disclosures' and the exact fields (politician info, transaction type, amount). No contradictions with 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 concise sentences with the key action ('Reverse lookup') front-loaded. Every word serves a purpose, no redundancy.

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?

Given the presence of an output schema and complete parameter documentation, the description effectively conveys the tool's function and return fields. It is sufficiently complete for an agent to understand usage.

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% for all three parameters, so the description's lack of additional parameter detail is justified. The description focuses on tool purpose rather than parameter syntax, which is appropriate at baseline.

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 verb 'find' and resource 'politicians recently traded a given TICKER'. It also specifies the output includes 'politician info, transaction type, and amount', making it distinct from sibling tools like get_politician_recent_trades which focus on politician-centric queries.

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 phrase 'Reverse lookup' signals the tool is for finding politicians from a ticker, contrasting with other tools. While it doesn't explicitly mention when not to use it, the context of sibling tools implies it's the go-to for ticker-based trade discovery.

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