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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context that results reflect filings 'as they post to lda.gov' (a live freshness source), but says nothing about ordering, result caps beyond the schema's limit, or update cadence.

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?

A single dense sentence front-loads the resource and source, then lists contents and filters. It is efficient with little waste, though the trailing field enumeration ('with client, firm, amount, issues and lobbyists') runs long.

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 pre-announces the returned fields (client, firm, amount, issues, lobbyists) and the data source, giving the agent enough to call it correctly for a read-only, filterable list tool. Ordering of results is the only notable omission.

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 baseline applies. The description's mention of filtering by kind, issue code, or a name maps directly onto documented parameters without adding syntax, defaults, or format detail beyond what the schema already provides.

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 (newest federal lobbying disclosures) with its source (lda.gov) and enumerates the filing kinds it returns (new registrations, terminations, quarterly reports, amendments), plus the fields included. This clearly distinguishes it from siblings like search_lobbying or state_lobbying, though no sibling is named explicitly.

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 phrase 'as they post' implies this is a freshness/latest-feed tool, and the optional filters are mentioned, but there is no explicit when-to-use guidance or exclusion telling the agent when to prefer search_lobbying or another sibling instead. Usage is only implied.

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