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

Beyond the readOnly/openWorld annotations, the description discloses critical behavior: pricing ($0.002 USDC per successful call), payment rails (x402 on Base, Solana, Arc), that failed calls are free, the dataset coverage per state, and that active licenses are returned by default. This is exactly the kind of context an agent needs before invoking a paid, read-only lookup.

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 a single, tightly packed paragraph that front-loads purpose, then state sources, then searchable fields, then pricing. Every sentence contributes actionable information, and the payment terms are placed at the end without burying the lede.

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?

Given a fully described 8-parameter schema and an output schema, the description fills the remaining gaps: data provenance, searchable fields, default active filtering, and the paid-call mechanics. Nothing an agent needs to decide to call or to interpret the result set 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 every parameter is already documented in the schema, and the description adds little parameter-level detail beyond reinforcing the search-by-license-number/name/city modes and the active-only default. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opens with a specific verb and resource: 'Veterinarian license verification from official state open data' and names the exact state sources (Colorado DORA, Illinois IDFPR). It clearly distinguishes itself from sibling license tools (nursing, dental, medical boards, NPI registry) by profession and state scope.

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?

It states the available search modes ('Search by license number, name or city') and the default behavior ('active licenses by default'), giving clear context for how to use it. However, it does not explicitly say when to prefer this tool over alternatives like health_npi_provider_registry or medical board tools, nor does it list exclusions.

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