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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds value by noting that NCDMV publishes no other machine-readable directory, establishing this tool as the definitive locator, and mentions that each office carries its district. This adds useful context beyond 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 very concise: two sentences plus example queries. It is front-loaded with the core purpose and every sentence adds necessary context. No wasted words.

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 no output schema, the description states what fields are returned (address, city, ZIP, phone, hours, district), which is sufficient for a read-only locator tool. It also explains the tool's unique role as the state's only machine-readable office directory.

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?

The input schema has 6 parameters with full descriptions (100% coverage). The description adds real-world usage examples (e.g., 'DMV offices in Raleigh') and elaborates on search by office name, city, or ZIP, enriching but not duplicating the schema. It goes beyond baseline by providing context for parameter usage.

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 finds NC DMV driver license offices and license plate agencies, providing address, city, ZIP, phone, and hours. It gives concrete examples of queries it answers, and distinguishes itself from the sibling tool nc_dmv_wait_times by specifying that for live queues that other tool should be used.

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 explicitly tells when to use this tool (for office location info), and when not (for live queues use nc_dmv_wait_times). It also lists search criteria: office name, city, or ZIP, providing clear guidance on usage scenarios.

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