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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the data is sourced from public LDA filings and the company's own report already includes its outside firms' fees — a double-counting trap an agent would otherwise fall into — plus a clear scope disclaimer that the data sits outside the score.

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?

The return contents are front-loaded in the first clause, followed by the double-counting caveat, then the disclaimer. It is appropriately sized for the amount of return detail conveyed, though the run-on first sentence could be split for scanability and the 'not investment advice' line is boilerplate rather than tool-specific.

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 in play, the description carries the return-shape burden and does so well, covering all three result components an agent would need to answer questions. The only soft gap is that nothing is said about empty results for companies without LDA filings or about non-US tickers, which matters for a public-records lookup.

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%, with 'limit' (1-50, default 10) and 'ticker' fully documented in the schema, so the baseline is 3. The description's reference to 'the most recent reports' weakly maps to the limit parameter but adds no format, bounds, or edge-case guidance (e.g., how companies with no filings are handled) beyond the schema.

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 definition leads with a specific verb and resource — 'Returns a company's US federal lobbying' — and names the underlying source (public Lobbying Disclosure Act reports). It then enumerates exactly what comes back (quarterly spend, latest complete quarter with year-over-year change, recent filings with filer identity and issue areas), which is unique among the sibling company tools and leaves no ambiguity about the resource.

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 only implied: an agent learns this is contextual data, not part of the Quantral score, and not investment advice. There is no explicit statement of when to reach for this versus get_company_score or get_company_signals when a user asks about a company's political activity, and no exclusions or prerequisites (e.g., invalid or non-US tickers) are given.

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