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

With no annotations and no output schema, the description carries the full burden and does disclose the return payload shape, including the exact performance metrics. It says nothing about ordering, truncation, or pagination behavior despite a limit parameter capped at 500, and no auth or rate-limit context is given.

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?

Two sentences, front-loaded with what is returned, followed by the one operational instruction the caller needs. No filler and no restatement of the tool name.

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 read tool with no output schema and no annotations, the description covers output content and the key input's provenance. The remaining gap is the unexplained limit/truncation behavior, which matters for members with large trade histories.

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%, so the description must compensate. It does well for member_slug, adding provenance (returned by get_congress_trades) and a format example ('nancy-pelosi'), but the limit parameter is never mentioned, leaving the agent to guess what it bounds and what happens at the 500 cap.

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?

Names a specific verb and resource: all disclosed trades for a single member of Congress, plus an enumerated performance summary (trade count, buys/sells, average per-share return). The single-member scope implicitly separates it from get_congress_trades and get_congress_stats, though it never states the contrast explicitly.

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?

Gives a concrete workflow prerequisite: 'Pass the member_slug returned by get_congress_trades', which routes the agent to the sibling first. It stops short of saying when to prefer get_congress_stats or what to do if the slug is unknown.

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