List domain privacy (WhoisGuard) subscriptions

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

Annotations already declare readOnlyHint=true, and the description reinforces it with 'Read-only.' It adds value beyond annotations by specifying what fields are returned (domain, status, expiry) and the account scope. It does not mention pagination behavior, but the schema covers page/pageSize, so this is acceptable.

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, front-loaded with the action and resource. Every clause adds useful information: what is listed, included fields, and where to go for toggling. This is exemplary conciseness.

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?

The tool is a straightforward list with output schema and annotations. The description covers the primary purpose, scope, and returned fields, making it sufficient for an agent to invoke correctly. The only gap is parameter semantics, which are already penalized in that dimension; overall the description is complete for the tool's complexity.

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 only 33% (only listType has a short description), and the tool description does not explain any parameters. The meaning of 'listType' with enum values (ALL, ALLOTTED, FREE, DISCARD) is only vaguely 'Filter subscriptions,' and page/pageSize are left to inference. Since the coverage is low, the description should compensate but does not.

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 verb ('List') and resource ('WhoisGuard/domain-privacy subscriptions'), scopes it to the account, and details included fields (domain, status, expiry). It also explicitly distinguishes from the sibling tool set_domain_privacy by pointing to it for toggling, making the purpose unambiguous.

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?

The description says 'Use set_domain_privacy to toggle a domain's privacy,' which explicitly names the alternative for a different action. This prevents misuse and clarifies when to use this tool versus its sibling. No other alternatives are needed given the input schema and sibling list.

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