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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral context by naming the Senate LDA source and specifying that results include client, registrant, period, income/expenses, and lobbying issues, going beyond the annotations without contradicting them.

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 compact and front-loaded with the core action and resource, followed by filter options and return contents. The closing sentence about pairing with FEC and Congress tools is useful context, though slightly tangential, so it is not perfectly minimal.

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?

Given no output schema, the description does a good job of telling the agent what results look like, and the schema documents all seven optional parameters. It is not fully complete because it does not mention pagination behavior, response size, or how this relates to the other lobbying_* sibling tools, but it is adequate for a read-only search tool.

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 100%, so the parameters are already well-documented in the schema. The description essentially restates the filter dimensions from the schema without adding new semantic detail such as matching behavior, defaults, or special values.

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 states a specific action ('Search') and resource ('U.S. federal lobbying disclosure filings (Senate LDA)'), and it lists the key filters and returned fields, so an agent can understand the tool's function. It does not explicitly differentiate itself from sibling tools like lobbying_detail, lobbying_lobbyists, or lobbying_registrants, which keeps it from a 5.

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 implies when the tool is useful by describing filters and return fields, and it suggests pairing with FEC and Congress tools. However, it does not explicitly state when to use this tool versus the lobbying_* siblings, and it offers no exclusions or alternative routing guidance.

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