put--v4-domains-name-verify

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Verify Domain' implies a read-only check, but it doesn't specify whether this is a simple status check, a configuration validation, or a more complex verification process. There's no information about permissions required, rate limits, or what happens during verification.

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?

While technically concise with just two words, this is under-specification rather than effective conciseness. The description fails to provide any meaningful information that would help an agent understand or use the tool properly. Every word should earn its place, but here the words don't earn their place by adding value.

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 tool with no annotations, no output schema, and 0% parameter documentation, the description is completely inadequate. It doesn't explain what verification means, what the tool actually does, what it returns, or how it differs from other domain-related tools. The context demands much more explanation than provided.

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?

With 0% schema description coverage for the single 'name' parameter, the description provides no compensation. It doesn't explain what format the domain name should be in, whether it needs to be a fully qualified domain, or any constraints on the input. The description adds zero semantic value beyond what's already in the bare schema.

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 'Verify Domain' is essentially a tautology that restates the tool name, providing no additional specificity about what verification entails. It doesn't specify what resource is being verified (domain ownership? configuration? deliverability?) or distinguish this tool from sibling tools that also operate on domains.

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 provides absolutely no guidance about when to use this tool versus alternatives. With multiple sibling tools operating on domains (get--v4-domains, get--v4-domains-name, various domain statistics tools), there's no indication of when domain verification is needed versus other domain operations.

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