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

Annotations already declare openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is partly covered. The description adds real context beyond that: it mutates external DNS records (CNAME/A/TXT) and performs SSL checks, and dryRun previews changes — telling the agent this reaches outside HighLevel's boundary. It stops short of stating reversibility, propagation wait times, or what a partial failure leaves behind.

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, front-loaded with the action and scope, followed by a compact usage example that earns its place by demonstrating dryRun. No filler or repetition of the title.

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 an open-world DNS mutation with no output schema, the description covers the workflow phases and the preview flag but omits what the tool returns (records to publish? propagation status?), how failures are surfaced, and the fact that no parameters are marked required yet the operation clearly needs domain + locationId.

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 100%, so all three parameters are already documented, making baseline 3 correct. The embedded example shows a plausible combination of domain/locationId/dryRun but adds no semantics about formats, constraints, or whether domain and locationId are effectively required despite required=[].

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?

Specific verbs (plan, verify, attach) against a concrete resource (HighLevel custom funnel domains, branded short-link DNS records with SSL). An agent immediately knows this is the domain/DNS onboarding tool. It does not name any sibling, but none of the listed siblings overlap this domain, so differentiation is implicit rather than stated.

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 three-phase framing (plan → verify → attach) and the dryRun example imply a preview-then-apply workflow, but there is no explicit statement of when to use this versus e.g. ghl_site_builder_sync, no prerequisites (agency vs. sub-account token), and no when-not-to-use guidance.

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