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

Beyond the annotations, it discloses failure semantics (SOURCE_STALE returns no verification, PAID_EXECUTION_REQUIRED yields a handoff) and a known data limitation (stale expired-registration source). It confirms no system mutation and idempotency against a certified snapshot — the idempotent/readOnly hint repetition is mitigated by the extra snapshot context.

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?

Front-loaded with purpose and usage, and every sentence carries substantive information. It is dense and somewhat long, with minor redundancy between the annotation idempotent hint and the text's idempotency claim, but no filler.

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 compensates fully by enumerating return contents (match status, bond coverage, name match basis, region resolution, suspension evidence, source dates) and by flagging the one unavailable data class. An agent has everything needed to call and interpret it.

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 baseline is 3, but the description adds practical selection logic for region (include only when similarly named entities may exist, omit when unknown), which the schema description does not state. business_name adds no detail 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?

States a specific verb and resource — read-only USDA Packers and Stockyards livestock counterparty verification — and enumerates the covered entity classes (buyer, dealer, market agency, packer). The scope is unambiguous even without siblings to differentiate from.

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?

Explicitly names triggering situations (pre-sale checks, transactions, procurement, vendor onboarding, recurring review) and equally explicit exclusions (not a credit score, solvency determination, legal conclusion, recommendation, or payment guarantee). It also gives conditional guidance for the region parameter.

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