set_custom_domain

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

No annotations are provided, so the description carries the full burden. It mentions the effect of priority display but does not disclose key behaviors such as whether it overrides existing settings, triggers validation, requires permissions, or is idempotent. This is insufficient for a mutation 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 two short sentences with no wasted words. It is front-loaded with the action and efficiently communicates the core purpose.

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 no output schema, no annotations, and sibling tools that check and clear, the description lacks important context. It does not cover idempotency, side effects, or prerequisites, leaving the agent with insufficient information to use the tool correctly in various scenarios.

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%, so baseline is 3. The description adds minimal value beyond the schema; the phrase '设置自定义子域名前缀' loosely aligns with the subdomain parameter but does not provide additional detail. The example in the schema description is more helpful.

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 tool sets a custom subdomain prefix for a specified website and mentions the effect of priority display. It is specific about the verb and resource. However, it does not explicitly differentiate from siblings like check_custom_domain or clear_custom_domain, though the distinction is implicit from the name.

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 implies usage for setting a custom subdomain, but lacks explicit guidance on when to use this tool versus checking or clearing. No alternative tools are mentioned, and no context about prerequisites or typical workflows is provided.

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