house_trades_by_ticker

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

No annotations are provided. The description shows the return format but does not disclose behavioral traits such as rate limits, data freshness, pagination, or what 'normalized' means. The burden is on the description, which is insufficient.

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 front-loads the response structure rather than key usage information. It could be more concise by stating the tool's primary function first.

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?

No output schema and low schema coverage. The description provides response structure but is incomplete for an agent to fully understand all parameters, edge cases, or constraints. Additional context is needed.

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%. The description does not explain parameters beyond the schema; it only shows the response structure. It adds minimal meaning for parameters like 'ticker' or 'limit'.

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 indicates the tool returns normalized US House trades for a ticker, and includes a detailed JSON structure. It distinguishes from several sibling tools like 'senate_trades_by_ticker' and screeners.

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 by showing parameters (ticker, date range, limit) but provides no explicit guidance on when to use this tool versus alternatives like 'senate_trades_by_ticker' or screeners.

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