TLD price list

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real value on top: prices are list prices (not checkout totals), USD-denominated, returned with source and timestamp, and unknown TLDs are explicitly reported as not found rather than estimated. That last clause is a meaningful anti-hallucination guarantee an agent needs. It omits rate limits and pagination/refresh behavior.

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?

Two tightly written sentences, front-loaded with what is returned and followed by the edge-case guarantee. No filler, no restatement of the name.

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 single-parameter read-only lookup with no output schema, the description adequately covers what comes back (per-TLD registration/renewal/transfer prices, source, timestamp) and the not-found behavior, with annotations covering the safety profile. Only the input TLD string format remains unspecified.

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 0%, so the description must carry the parameter burden; 'per TLD' does indicate the array's meaning, but it never specifies accepted format (e.g. 'com' vs '.com'), case handling, or acknowledges the 40-item cap in the schema. It partially compensates but leaves format ambiguity.

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 resource and breakdown: 'Registration, renewal and transfer list prices (USD) per TLD', plus the data source (Porkbun's public pricing API). This is far more concrete than a generic 'get pricing' and is clearly distinct from the availability/DNS/SSL siblings, though it never names or contrasts 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?

There is no when-to-use guidance: nothing says to call this before prepare_purchase_link or as a complement to check_availability, and no prerequisites or exclusions are given. The provenance note ('public pricing API') is context, not usage routing.

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