Verify Custom Domain DNS

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

The description discloses that the tool persists results and checks CNAME, adding value beyond annotations. However, it contradicts the readOnlyHint=true annotation by stating it modifies state, creating confusion. The description is accurate but the annotation conflict lowers the score.

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 concise with two sentences explaining functionality and a hint about A records, plus cost info. It is front-loaded and efficient, but missing the promised example for the body parameter.

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 has no output schema, and the description does not detail the return format beyond mentioning A records as hints. The parameter is also insufficiently documented. With one parameter and no output schema, the description should provide more context to be complete.

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 describes the body parameter as 'Raw JSON body — see the example in the tool description for required fields,' but the tool description does not include any example or list of fields. The agent has no guidance on what to include in the body, making parameter semantics extremely poor.

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 states the tool checks if the custom_domain has a CNAME pointing to api.astroway.info, persists the result, and provides hints for A records. It is distinct from siblings like whitelabel_logo and whitelabel_preview, which handle other whitelabel settings.

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 implies the tool is used for verifying custom domain DNS, but it does not explicitly state when to use it or contrast it with alternatives. The context of whitelabel tools makes it obvious, but no explicit guidance is given.

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