US Senate stock trades

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

Annotations already clearly indicate read-only, idempotent, non-destructive behavior. Description adds that results are sorted by most recent matches, but no other behavioral details. No contradiction 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?

Description is brief, front-loaded with purpose, includes an example in efficient manner. No superfluous text.

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?

Description covers filtering options and ordering. No output schema exists, so it would be helpful to mention result fields, but the purpose is clear. With annotations providing safety, the description is complete enough for basic 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 provides descriptions for 4 of 5 parameters (80% coverage). Description lists filter types and includes an example that demonstrates parameter usage. No additional parameter meaning beyond schema, but example aids understanding.

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 explicitly states 'US Senate stock transactions', lists filter criteria, and includes an example. It distinguishes from the sibling 'congress_house_trades' by the Senate vs House distinction.

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?

Description implies usage for querying Senate trades with filters and includes an example. Does not explicitly mention when to use alternatives like congress_house_trades, but the context is clear.

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