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

Annotations already establish read-only, idempotent, and open-world behavior, and the description adds a valuable non-obvious limitation: paper-filed reports are counted but not read. It also clarifies the data source and what enriched fields are returned. It stops short of a 5 because it does not mention pagination, rate limits, or other potential runtime behaviors.

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 two tight sentences with no filler. The first sentence front-loads the action and the key output features, and the second sentence adds the paper-filing caveat. Every part contributes useful information.

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 an 8-parameter tool with no output schema and very low parameter coverage, the description gives a helpful summary of returned data and the main caveat, but it does not explain how filters interact or what the response shape looks like. It is adequate for simple calls but not fully complete for nuanced queries.

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?

With only 13% schema description coverage, the description needed to compensate for the eight optional parameters, but it does not explain side, year, limit, owner, assetType, or minAmount. It only hints at ticker and member as relevant concepts through 'ticker and member summaries,' which is output-oriented rather than parameter-oriented.

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 opens with 'Get senator transactions from electronic Senate periodic transaction reports,' a specific verb and resource that clearly distinguishes this from the House-focused sibling congress.house_trades. It also enumerates the included enrichments such as ticker/member summaries, stock returns, state, party, and committees, making the tool's scope unambiguous.

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 Senate scope and the electronic-report caveat imply when this tool is appropriate, but the description does not explicitly name alternatives or state when not to use it. It mentions that paper-filed reports are counted but not read, which is a limitation, but it never tells the agent to use congress.house_trades for House disclosures.

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