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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds useful behavior of its own — the composed payload (rankings plus YoY change) and the default-quarter resolution — but says nothing about freshness, caching, or how the default quarter is determined.

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 tight sentences, front-loaded with what the tool returns and ending on the default behavior. The enumeration is dense but every item is a real output component, so nothing is wasted.

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?

With a read-only, optional-parameter tool and no output schema, the description usefully enumerates the return payload and the no-argument default, which is close to sufficient. The remaining gap is parameter semantics, which neither schema nor description fills.

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 0% (only min/max bounds, no descriptions), so the description must carry the parameter burden. It only implies that year/quarter are optional via the default statement; it never explains what quarter means, accepted values, or how out-of-range or future quarters are handled.

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 names a specific resource and enumerates exactly what is returned: total lobbying spending, top firms by income, top spenders, busiest issues, plus year-over-year change. That is far more concrete than a tautology, though it never names or contrasts a sibling like industry_lobbying or state_lobbying to steer selection.

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?

It supplies a default-quarter behavior ('Defaults to the latest quarter whose reports are due'), which tells the agent it can call with no arguments, but gives no explicit when-to-use versus alternatives in a sibling set full of site-specific lobbying tools.

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