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

With no annotations, the description carries the burden. It discloses the verification mechanism (snippet or DNS TXT record) and the read-style nature ('checks'), which is useful. It does not address side effects, auth prerequisites, rate limits, or what the response indicates, leaving some behavioral gaps.

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?

A single sentence conveys the action, target, and mechanism with zero filler. The key scoping (pending website) is front-loaded, and the parenthetical adds explanatory detail without bloating the description.

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 one-parameter tool with no output schema, the description covers the essential what, when, and how. It does not explain the return value or failure behavior, but an agent can invoke it correctly with only a domain.

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 only parameter, 'domain,' has no schema description (0% coverage), so the description must compensate. It implies domain is the website being verified but never mentions the parameter or its expected format (e.g., bare domain vs. protocol). It provides partial context but not full parameter semantics.

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 opens with a specific verb and resource: 'Verify ownership of a pending website.' It adds the mechanism ('checks the installed snippet or DNS TXT record'), which makes the tool's function unmistakable and separates it from the analytics and reporting siblings like get_stats and get_visitors.

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?

It clearly targets 'pending website,' situating the tool in the site-onboarding flow after a site has been added but not yet verified. It does not explicitly name alternatives or say when not to use it, but the context is clear enough against the sibling set.

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