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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world (openWorldHint=false). The description adds real behavioral context beyond that: the 12-month lookback window and the ranking methodology by disclosed activity count. It does not describe pagination or result size limits, so it stops short of a 5.

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, front-loaded with what the tool returns, followed by what the issue parameter means. No redundant restatement of the title or annotations.

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-parameter, read-only tool with no output schema, the description conveys the result shape (ranked firms/lobbyists), the time scope, and the parameter domain. Missing only edge behavior such as result limits or handling of unknown issue values.

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%, so the baseline is 3, and the description goes further by explaining that issues are 'LDA general issue areas' and enumerating representative values (Health Issues, Defense, Taxation, Energy). This clarifies the domain of the otherwise loosely constrained issue string.

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?

States a specific resource (lobbying firms and lobbyists), a specific dimension (a policy issue), a time window (past 12 months), and a ranking basis (number of disclosed lobbying activities). An agent can distinguish this from who_lobbies_agency and who_lobbies_on_bill, which address agencies and bills rather than issue areas.

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 implied by the description (use it to find who is active on a policy issue), but there is no explicit when-to-use/when-not guidance and no routing to alternatives like industry_lobbying or search_lobbying. Adequate but leaves selection to inference.

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