senate_trades_by_ticker

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

No annotations are present, so the description carries full burden for behavioral disclosure. It only shows output format and does not mention side effects, permissions, rate limits, or behavior for missing tickers.

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 is short but misuses space by showing an output structure rather than stating purpose. It is not front-loaded with a clear action statement.

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 tool with nested parameters and siblings, the description is severely incomplete. It lacks explanation of what the tool does, how to use parameters, and return value semantics beyond a cryptic JSON sample.

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% (only date_from and date_to have minimal descriptions in the schema). The description adds no information about parameters like 'ticker', 'limit', or 'format'.

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 'Normalized US Senate trades' is a noun phrase without a verb; it does not explicitly state that the tool retrieves or lists trades by ticker. It fails to differentiate from sibling tools like 'house_trades_by_ticker' which have a similar name pattern.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions.

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