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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds that it covers all 60 offices, returns appointment-only status and ODOT link, and hints at pagination via the limit parameter default. No contradictions.

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 five sentences, each adding value: purpose, fields, coverage, usage examples, and sibling differentiation. No fluff or 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?

No output schema exists, so the description must explain return data. It lists all significant fields (address, phone, lat/lng, region, appointment-only, ODOT link) and states the total coverage. The limit parameter behavior is implied. Slightly lacking on return format details, but sufficient for a simple query tool.

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 baseline is 3. The description mentions filtering by city, ZIP, region, or office name but does not add significant semantics beyond what the schema already provides for each parameter.

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 starts with 'Find Oregon DMV field offices' – a specific verb and resource. It lists the fields returned and explicitly differentiates from sibling tool 'or_dmv_wait_times' by directing users there for queue lengths.

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 provides clear examples of queries it answers (e.g., 'DMV office in Eugene', 'address and phone for the Bend DMV') and explicitly states when to use the sibling instead: 'For the live queue length at these same offices use or_dmv_wait_times.' No ambiguity.

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