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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds useful return scope—'clients in the past year' and 'government positions they disclosed'—but does not cover error behavior, authentication, or rate limits, which is a moderate addition beyond structured fields.

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 with no filler. The content list is front-loaded and the input acceptance is brief, making it appropriately sized for a simple lookup tool.

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 simple one-parameter lookup with rich annotations and no output schema, the description adequately covers what the tool returns and what input it expects. It omits edge cases like unknown identifiers, but nothing critical to correct invocation is missing.

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 single parameter is already documented. The description adds the namespace 'Gov Relations slug' beyond the schema's 'Lobbyist name or slug', but otherwise largely repeats the schema and provides no additional syntax or handling details.

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 (registered federal lobbyist) and enumerates the returned attributes (current firm, clients in past year, main issues, disclosed government positions). This clearly distinguishes it from generic search tools, though it does not explicitly differentiate from siblings like get_client or get_firm.

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?

Provides no guidance on when to use this tool versus alternatives like get_firm, get_client, or state_lobbying. It only states accepted input formats ('Gov Relations slug or a name'), leaving routing decisions entirely to the agent.

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