Danh mục đuôi tên miền theo ngành

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: 'Không cần đăng nhập' (no authentication required) and a summary of what each returned group contains (count and price range).

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, no filler, with the output content front-loaded and the workflow instruction second. Every clause earns its place.

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 input parameters and no output schema, the description carries the burden of describing the return value, and it does so (industry groups with TLD counts and VND price ranges) while also explaining its role in the domain-purchase workflow and its auth requirement.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is needed and instead frames the tool as a prerequisite lookup that yields the 'slug ngành' value later tools consume.

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 ('Liệt kê' / list) and resource ('các nhóm ngành của đuôi tên miền'), plus the concrete payload (number of TLDs and VND price range per group). It also names the sibling cloud_domain_tlds as the downstream consumer, so an agent can distinguish it from other domain tools without opening a schema.

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?

Explicitly instructs to call this BEFORE cloud_domain_tlds to obtain the industry slug needed for filtering, which is a clear ordering rule against a named alternative. It does not state when NOT to use it or any failure conditions, so it stops short of full when/when-not coverage.

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