congress_trades

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

The description adds the key behaviors 'recent' and 'optionally filtered to one ticker' despite absent annotations. It does not define what 'recent' means, how results are ordered, or what happens when ticker is omitted, leaving room for stronger disclosure.

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?

One concise sentence with no filler. The key qualifiers 'recent' and 'optionally filtered to one ticker' are front-loaded and every word earns its place.

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 two-parameter, non-nested read tool with an output schema, the description covers the core operation and ticker behavior. It remains slightly ambiguous on the recency window and limit semantics, but those are minor for tool selection and invocation.

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 description explains the ticker parameter's purpose, adding value beyond the raw schema. The limit parameter is not described at all, though its name and default of 50 make its purpose inferable; at 0% schema coverage the description could have done more.

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?

Clearly identifies the resource (congressional trades) and a scoping behavior (filter by ticker), which differentiates it from the sibling tools. Lacks an explicit verb such as 'get' or 'list', so it stops short of the strongest 5 rating.

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 when-to-use guidance or alternative tools are mentioned. The intended context is implied by the resource name and the optional ticker filter, but the description never says why an agent should choose this over sibling tools like flow_alerts or dark_pool.

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