Add Custom Portal Domain

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description adds value by stating it returns DNS records and requires configuration at the registrar. It does not contradict annotations. Behavioral traits like permission requirements or failure outcomes are not covered, but annotations already provide basic safety profile.

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 two sentences per language, front-loading the purpose and return value. Every sentence provides useful information (purpose, return, example). No fluff.

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?

Given the tool's simplicity (2 params, no output schema), the description covers the main behavior: adding domain, returning DNS records, and the need to configure before verification. It does not mention constraints (e.g., uniqueness, validation) but is adequate for selecting and invoking the tool.

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 coverage is 100% with descriptions. The tool description adds an example for the domain parameter and repeats defaults for workspaceId, which adds marginal value beyond schema. No enums or nested objects exist, so the description suffices.

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 action (add), resource (custom domain to Frihet client portal), and purpose (white-label branding). It returns DNS records and distinguishes from siblings like remove or verify by specifying the return value and post-configuration step.

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 guides usage by mentioning that DNS records must be configured before verification, implying a sequence. An example is provided. However, it does not explicitly state when to use this tool vs alternatives (e.g., verify) or list prerequisites.

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