set_domain_force_https

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

No annotations provided. The description only repeats the tool's name without disclosing behavioral traits such as side effects, required permissions, or return behavior. For a mutation tool, this is insufficient.

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?

Single sentence, front-loaded with the purpose. Waste is minimal, though it could be slightly more informative without bloat.

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?

No output schema and no annotations. The description does not explain what the tool returns, error conditions, or prerequisites (e.g., domain must have HTTPS enabled). Incomplete for an action 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% so the description adds no extra meaning beyond the parameter descriptions. Baseline 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 '设置域名强制 HTTPS 跳转' (Set domain force HTTPS redirect) clearly states the verb 'set' and resource 'domain force HTTPS', distinguishing it from other set_domain_* tools like set_domain_https or set_domain_cache_policy.

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?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., domain must exist), nor does it compare to related tools like query_domain_force_https or other set_domain_* tools.

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