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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that it returns only links (never the PDF), explains the page/pdf key semantics, reveals the 'only labels we already hold' constraint for Toyota, Lexus, Nissan and Infiniti, and states that no API key is needed. This is rich behavioral context that the annotations alone do not provide, and nothing contradicts the 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 four sentences and front-loaded: core purpose first, then return format, then coverage caveat, then auth. Each sentence adds distinct value; the only minor redundancy is restating '17-character VIN' from the schema, and the 'Free, no key' tag is efficient and useful.

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?

For a one-parameter, read-only tool with an output schema present, the description covers purpose, return semantics, make-specific coverage limits, and auth requirements. It does not specify behavior when no sticker is found, but the sibling why_no_sticker plausibly covers that case, and the output schema documents the return structure.

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% — the schema already documents the 17-character VIN, the forbidden letters I/O/Q, and requiredness. The description mostly restates the 17-character constraint and adds a modest extra: the 'NHTSA specification decode,' which implies validation of the input. Since the schema carries the full parameter burden, the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Look up the original factory window sticker (Monroney label) for a 17-character VIN.' It goes beyond the title by naming the Monroney label, the NHTSA decode, and the key return behavior (links, not PDFs), which distinguishes it from siblings like which_makes_are_covered and why_no_sticker.

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 context (free, no key, coverage limits for four makes) but never explicitly routes the agent to alternatives. It implies usage — use this tool to fetch a sticker — yet does not say 'use which_makes_are_covered to check coverage' or 'use why_no_sticker when no label exists,' so when/when-not guidance is only implicit.

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