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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses additional behavioral traits: it is experimental, may change or be withdrawn, is not covered by the accuracy eval, and costs $0.05 per call. It also describes the output content and ordering, providing useful context for an agent. No contradiction with annotations.

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 description is concise, consisting of two sentences. The first sentence front-loads essential caveats (experimental, may change) before specifying the core function, and the second adds cost. Every sentence carries significant information without redundancy.

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?

Despite lacking an output schema, the description covers the main output fields (registrant, income/expenses, issue areas), ordering, and experimental status. It also mentions cost. While it does not specify exact return format or pagination details, the description provides sufficient information for an agent to call the tool reasonably. Given the tool's experimental nature and simplicity, this is adequate.

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 all parameters (company, year, limit) are already documented in the schema. The description adds marginal parameter context by mentioning 'for a client company' and 'newest first', but does not explain syntax or edge cases beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool retrieves US Senate LDA lobbying disclosures for a client company, specifying the key data fields (registrant, income/expenses, issue areas) and ordering (newest first). This is a specific verb-resource combination that distinguishes it from sibling tools like insider_trades or government_contracts, making the purpose unambiguous.

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 description lacks explicit guidance on when to use this tool versus alternatives. It only mentions being experimental and outside the core SEC path, which hints at limited reliability but does not name alternative tools or exclusion conditions. An agent must infer the appropriate use from the domain-specific wording.

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