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

With no annotations, the description carries the full behavioral burden, and it does disclose a meaningful data-quality caveat: Senate counts since October 23, 2026 are partial. However, it defers detail to external 'server instructions' and says nothing about how counts are derived (trades vs filings), duplicate handling, or the shape of the returned breakdown.

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, zero filler, and the core capability is front-loaded before the caveat. Each sentence earns its place: one defines the output, the other flags a correctness risk.

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 single-optional-parameter count tool with no output schema, the description covers what is returned (counts split House/Senate) and the main caveat. The one gap is that it offloads the partial-data explanation to external server instructions rather than stating the effect on the numbers here.

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 coverage is 100% and the 'days' parameter already documents the look-back window and the 45-day disclosure lag. The description reinforces this by calling it an optional date filter, so the agent understands omitting it means no window, adding a small amount of meaning beyond the schema.

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 uses a specific verb+resource, 'Get counts of the trades ... broken down by chamber (House vs Senate)', so the agent knows exactly what aggregate it returns. The chamber facet implicitly separates it from get_party_breakdown, but no sibling is named explicitly, so it stops short of full differentiation.

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?

Usage is only implied: an agent infers this is the tool for chamber-level aggregates and the 'optional date filter' phrasing hints at an unfiltered all-time default. There is no explicit when-to-use versus get_party_breakdown/get_aggregate_stats guidance and no stated prerequisites or exclusions.

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