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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds value by disclosing the response contents (validity, score, suggested correction), but says nothing about how correction suggestions should be applied, whether calls are rate-limited, or what happens on malformed input.

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?

One front-loaded sentence that names the tool's action and its three outputs, followed by a terse endpoint reference. The 'GET /addressvalidation' fragment is only marginally useful to an agent but is not enough to hurt readability.

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?

With no output schema, the description usefully compensates by enumerating the response fields. Given 6 well-documented parameters and full annotation coverage, the remaining gap is minor — chiefly what a 'failed' validation means and whether the corrected address is authoritative.

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% with constraints (maxLength, country_code pattern) fully documented, so the schema carries the parameter burden. The description adds no meaning beyond the schema, which is the baseline expectation here.

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?

States a specific verb and resource (check a shipping address) plus the three things it returns: validity, a score, and Gooten's suggested corrected address. This makes it clearly distinct from sibling tools like gooten_get_shipping_estimate or gooten_list_shipping_countries, though it never names those siblings explicitly.

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?

Usage is only implied — an agent can infer this is called before quoting or placing an order. There is no explicit 'use this when...' statement, no mention of prerequisites (e.g., needing a full order address), and no named alternatives.

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