domainForwardSubDomain

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

No annotations are provided, so the description bears the full burden of disclosing behavior. 'Create or update' signals mutation but does not explain whether existing forwards are overwritten, whether the operation is idempotent, what response to expect, or whether special authorization/account settings are needed. This is a significant gap for a state-changing tool.

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 extremely concise and front-loaded with the core action and resource. It includes a reference link without adding verbose filler, so every part earns its place.

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?

With 8 parameters, 5 required, no output schema, and no annotations, the description is too sparse to fully enable correct invocation. An agent still lacks guidance on how create versus update behavior is decided, what the redirect semantics imply, and what a successful result returns. The generic API reference link helps only if accessed externally.

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 has 100% description coverage, so the schema already documents all parameters. The tool description itself adds no additional parameter-level meaning, but because the schema carries the burden effectively, a baseline score of 3 is appropriate.

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 states a specific action ('Create or update') and a specific resource ('subdomain forward'), which distinguishes it from the sibling tool domainForwardSubDomainDelete and generally from domainForward by naming the subdomain scope. It does not explicitly contrast it with the sibling domainForward tool, so it falls just short of a 5.

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 gives no guidance on when to use this tool versus the sibling domainForward tool or when a delete operation would be more appropriate. There is no mention of prerequisites, idempotent behavior, or conditions that would make a create versus update distinction relevant.

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