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

Annotations already declare readOnlyHint, openWorldHint, etc. The description adds valuable behavioral details: data source ('published by NCDMV itself'), refresh rate ('refreshed continuously'), and special case outside business hours ('idle queue rather than a measurement'). This exceeds annotation coverage.

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 paragraph but packs all essential information: purpose, data source, example queries, parameter notes, and edge case behavior. Slightly verbose on the 'only two states' fact, but still efficient overall.

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 5 parameters, no output schema, but rich annotations, the description covers all critical aspects: what it does, what data it returns, parameter semantics, edge cases (closed offices), and realistic usage scenarios. No gaps identified.

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?

With 100% schema coverage, the description still adds value by explaining parameter usage, e.g., 'case-insensitive office-name substring' for 'office', 'wait ranks shortest average wait first' for 'sort', and default values for 'service' and 'limit'. This enriches understanding 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?

The description clearly states the tool provides 'live wait times at North Carolina DMV offices' with specific metrics (average wait, longest wait, open status). It distinguishes itself from sibling tool 'nc_dmv_offices' by focusing on live data and includes example queries, making the purpose unmistakable.

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 gives good context on when to use the tool (e.g., checking wait times, finding shortest line) and mentions behavior outside business hours. It does not explicitly compare to alternatives like 'nc_dmv_offices' but implies the distinction through its focus on live data.

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