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

With no annotations, the description carries the behavioral burden. It discloses the ordering (newest disclosure first), pagination behavior (limit up to 50, offset), optional filtering, and that each row links to the original filing document. It does not mention rate limits or authentication, but those are not obviously critical for this read-style list endpoint.

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, no filler. The core resource and ordering are front-loaded, followed by filtering, pagination, and per-row provenance information. Every sentence 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 list endpoint with four optional parameters, the description is largely complete: it covers scope, ordering, filters, pagination, and row content links. Since there is no output schema, it could have added more detail about returned fields, but the existing description is enough for an agent to select and invoke the tool correctly.

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 so by explaining ticker and/or member_id as filters and by noting limit and offset for pagination. It does not state defaults or value formats, but the schema already encodes the numerical bounds and the parameter names are self-explanatory.

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 states a specific verb and resource: disclosed congressional stock trades, newest disclosure first, with optional ticker and member_id filtering. It also adds concrete details like pagination and source links, which clearly differentiates it from sibling listing tools.

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 gives clear usage context: list trades when you want disclosed congressional stock transactions, optionally filtered by ticker or member_id, with pagination. It does not explicitly name alternatives or exclusions, but the filter and pagination details make the intended use obvious.

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