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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's real contribution is describing the shape of the result (top orgs, combined spending, top firms by client count), which is valuable given no output schema, but it says nothing about sorting limits, time granularity beyond '12 months', or data sources.

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?

One front-loaded sentence that leads with the primary output and ends with the no-argument fallback; nothing is padded. Slightly dense with three parallel list items but still efficient.

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 no output schema, the description usefully enumerates what comes back (organizations, combined spending, firms with most clients), which is the main gap it needs to fill. An agent can call it correctly; only edge details like result limits or ranking criteria are absent.

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% and the single parameter is fully documented with examples, so the baseline is 3. The description's 'call with no industry' note duplicates what the schema already states, adding no syntax or format detail beyond it.

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?

Names a specific resource and scope: an industry's federal lobbying over 12 months, the top-spending organizations, combined spending, and leading firms. This distinguishes it from the entity-level siblings (get_client, get_firm, get_lobbyist) by making 'industry' the aggregation axis, though it never explicitly names those alternatives.

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?

Gives one concrete usage condition: 'Call with no industry to list the industries available,' which resolves the zero-required-parameter ambiguity. It offers no when-not guidance or explicit routing against siblings like who_lobbies_on, so it stays short of a 5.

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