deployado_set_primary_domain

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the mutation/idempotency profile is covered. The description adds the useful consequence that the primary domain drives redirects, but omits what happens to the previously primary domain (demoted? left in place?) and whether verification is required.

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 short sentences, front-loaded with the action, zero filler. The redirects sentence is the only one that could be questioned, but it does add behavioral context.

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 small two-parameter tool with full schema coverage, rich annotations and no output schema, the definition is adequate but not complete: it does not cover the previous-primary-domain side effect, preconditions, or return behavior, which an agent would want before mutating state.

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% and both parameters (app_id, domain_id) are documented as UUIDs, so the baseline is 3. The description adds no further meaning about how the IDs are obtained or any cross-parameter constraints.

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?

States a specific verb and resource ('Set a domain as the primary domain for an app') and clarifies the effect ('used for redirects'). It is distinguishable from add_domain/remove_domain/list_domains by the 'primary' qualifier, though it never names those siblings explicitly.

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 intent is implied by the name and the redirects note, but there is no explicit guidance on when to call this versus deployado_add_domain or deployado_verify_domains. No prerequisites are stated, such as whether the domain must already be added and verified before it can be promoted.

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