verify_domain

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

No annotations are provided, so the description must convey behavioral traits. It states that the tool checks DNS propagation and SSL status, which implies a read-only operation, but it does not explicitly disclose side-effect freedom, response format, or any prerequisites such as domain ownership. The description is adequate but not rich in behavioral context.

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?

The description is a single concise sentence followed by a clarifying example. It front-loads the purpose and avoids repetition of the tool name or schema details. Every element 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?

The tool is simple with only two parameters and full schema coverage, but there is no output schema, so the description should hint at what the tool returns. The example suggests a 'verified' outcome, but the description doesn't describe the result format, potential errors, or behavior during propagation delays. This is a moderate gap.

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 input schema covers both parameters (site_id, hostname) thoroughly, so the baseline is 3. The description adds little beyond the schema—only the example 'example.com' reinforces the hostname parameter. It does not clarify site_id or any parameter relationships beyond what the schema already states.

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 identifies the tool's function with a specific verb ('Check') and resource ('DNS propagation and SSL status for a custom domain'). It also gives an example, making the purpose immediately obvious. This distinguishes it from sibling tools like add_domain or remove_domain.

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 clear context for when to use the tool via the example ('Check if example.com is verified'). It doesn't explicitly state when not to use it or mention alternatives, but the context is unambiguous enough for an AI agent to select it appropriately.

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