Verify Custom Portal Domain

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds useful behavioral context: returns status (pending/verified/failed) and DNS errors, plus propagation delay. No contradictions.

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 in English repeated in Spanish. Front-loaded with purpose, but the bilingual duplication adds unnecessary length. Could be more concise by dropping the Spanish repeat.

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?

Covers input, process, output, retry guidance, and references the prerequisite tool. No output schema needed; the description sufficiently explains expected return values.

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?

Single parameter 'domain' with schema coverage 100%. Schema already describes it. Description adds no extra semantic information beyond the 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?

Specifically states the verb 'Verify', the resource 'custom portal domain', and the scope 'DNS propagation'. Clearly distinguishes from sibling tools like frihet_portal_domain_add and frihet_portal_domain_remove.

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?

Gives explicit context: used after domain added via frihet_portal_domain_add. Recommends retry if pending, with a 48-hour propagation note. Lacks explicit when-not-to-use, but sibling set makes it clear.

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