Toggle HTTPS redirect

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

Annotations already signal readOnlyHint=false, idempotentHint=true, and destructiveHint=true. The description adds value by disclosing the certificate prerequisite, the 422 error condition, and the asymmetry between enabling (requires cert) and disabling (always accepted). These go beyond what annotations provide.

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?

Three sentences with no filler. The main action is front-loaded, followed by idempotency, then prerequisites and error conditions. Every sentence 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?

For a simple toggle tool with no output schema, the description covers the key behavioral details: what it does, when it does nothing, when it errors, and the prerequisite. It doesn't mention return values or the meaning of `username`, but those are minor gaps given the tool's simplicity and existing annotation coverage.

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% with each parameter described. The description enriches `is_enabled` by explaining that `true` requires a certificate while `false` is always accepted, adding behavioral nuance not present in the schema. It doesn't add much for `username` or `domain`, but the schema already covers them at a basic level.

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 explicitly states what the tool does: turns the HTTP-to-HTTPS redirect on or off based on `is_enabled`. The resource (HTTPS redirect of a website) is specific and clearly distinguishes it from sibling toggle tools like cache, maintenance mode, or cacheless mode.

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 clear operational guidance: turning the redirect on requires an installed certificate and will return 422 otherwise; turning it off is always accepted. It also notes the idempotent behavior of doing nothing when already in the requested state, which helps the agent decide when calling is appropriate. It doesn't explicitly name alternative redirect-creation tools, but the context is clear.

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