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

With no annotations available, the description carries the full behavioral burden and does a good job: it explains the three timestamp fields, the ~45-day STOCK Act disclosure delay, and the key limitation that Senate data is parsed to ticker level while House filings are metadata only. It does not cover rate limits, pagination, or return formatting, but the most decision-relevant behaviors are disclosed.

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 appropriately sized at four sentences, each serving a distinct purpose: scope/source, field definitions, temporal semantics, and data-granularity caveat. It is front-loaded with the primary function and contains no filler or repetition. This is a model of concise, information-dense documentation.

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 tool with four optional filters and no output schema, the description provides the return record fields and critical data-quality caveats, which is sufficient for an agent to invoke it correctly. The main gap is the absence of pagination, result limits, ordering, or a note about what 'metadata only' means for House records, which prevents a perfect score.

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 already describes three of the four parameters (name, since, ticker), leaving chamber with only enum values. The description adds important semantic nuance beyond the schema: the Senate-vs-House granularity difference affects how ticker and chamber filters behave, and the disclosed_at guidance clarifies the intended meaning of since for temporal filtering. This goes beyond the structured schema coverage.

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 identifies the resource (US Congress stock transactions) and its sources, and implies a query/list operation even though no explicit verb like 'list' or 'get' is used. The domain (Congress) and mention of Senate vs House data distinguish it from the sibling tools focused on ETF flows and insider trades, though that contrast is not explicitly stated.

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 no explicit 'when to use this vs alternatives' guidance. However, it implies the intended use case through domain-specific context, and it offers concrete usage advice about using disclosed_at rather than happened_at for point-in-time work. No exclusions or alternative tool names are mentioned, so usage guidance is mostly implied rather than direct.

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