Get domain pricing

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

Annotations already declare readOnlyHint=true, and the description adds the important behavioral caveat that these are standard non-premium prices. It also mentions the distilling behavior and per-year price tiers, going beyond the safety annotations to describe data 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 sentences with front-loaded purpose, a behavior note, and a helpful alternative pointer. 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?

With full schema coverage and an output schema present, the description provides the necessary usage context, caveats, and sibling differentiation. It is complete for a simple read-only pricing tool.

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% with described parameters, so baseline is 3. The description adds minimal parameter meaning beyond restating action options; it does clarify that the result is per-year tiers, but this is more output than input semantics.

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 'Get Namecheap's list price for one or more TLDs and an action' with explicit resource and scope. It distinguishes itself from the sibling tool by explicitly directing premium-domain pricing to check_domain_availability.

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?

Provides explicit guidance with 'for premium domains use check_domain_availability, which returns premium pricing' as an alternative. Also indicates the tool distils users.getPricing, suggesting it is a focused subset for standard prices.

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