Bảng giá đuôi tên miền

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: prices already include VAT, first-year price reflects running registry promos, .vn entries carry needs_verification=true meaning an entity-verification profile is required, and no login is needed.

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?

Front-loads what is returned (both price fields, VAT-inclusive) before the filtering options and the when-to-use triggers. Dense but every sentence carries distinct information; slightly long but not padded.

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 carries the return-value burden and does name the key output fields (price_vnd, renew_vnd, needs_verification). Filters, auth requirement, and the group-slug dependency are all covered, leaving only minor gaps such as pagination guidance.

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%, so the baseline is 3, but the description adds value the schema lacks: group takes a slug sourced from cloud_domain_tld_groups, q matches both the TLD name and Vietnamese label, and max_price_vnd filters on the first-year price specifically rather than renewal.

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 resource and scope: the full price list of TLDs MONA Domain sells, with first-year (price_vnd) and renewal (renew_vnd) prices in VND incl. VAT. It is the only price-list tool among the cloud_domain_* siblings and it clarifies its relationship to cloud_domain_tld_groups (source of group slugs).

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?

Gives concrete trigger phrases ('có những đuôi nào', 'đuôi nào rẻ', 'đuôi nào hợp ngành X') and routes the agent to cloud_domain_tld_groups for valid group slugs. It does not explicitly exclude or compare against cloud_domain_search / cloud_domain_suggest, so the when-not side is left to inference.

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