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

No annotations are provided, so the description carries the full burden. It mentions the cost per call ($0.05/call) and the type of data returned (transactions, politician, ticker, amount, date), but it does not disclose details about response format, error handling, rate limits, or potential side effects. The description is adequate but not rich in behavioral detail.

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 compact and front-loaded with the core purpose. It packs the parameter list into a single sentence, which is somewhat dense but efficient. The example at the end aids comprehension. It could be more structured (e.g., bullet points) but remains concise and readable.

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 that the schema provides no parameter definitions, the description covers all the necessary parameter details and includes an example. It does not mention output format or error behavior, but for a data lookup tool this is arguably sufficient. The absence of explicit optional/required flags for parameters is a minor gap, but the example helps infer typical 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?

The schema only defines a 'params' object with additionalProperties, leaving all parameter semantics to the description. The description thoroughly explains each parameter: politician (name substring), ticker (exact), chamber (house|senate), dateRange (format with example), type (substring with examples), and maxItems (integer). This fully compensates for the lack of schema detail.

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 tool's purpose: 'US congressional stock trades' with details about the STOCK Act and the data fields (politician, ticker, amount, date). This is specific and distinguishes it from generic search tools. It also includes pricing, which further clarifies its role.

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 does not explicitly mention when to use this tool versus alternatives. It provides an example query ({'ticker': 'NVDA', 'chamber': 'house'}) but no comparative guidance. Since there are no sibling tools dedicated to congressional trades, the need for explicit differentiation is lower, but the dimension asks for when-to-use guidance, which is missing.

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