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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the mutation risk is covered structurally. The description adds genuine context the annotations don't carry — the auth requirement (key or sign-in) and the nuance that it 'stops serving' rather than deletes. However it never says whether this is reversible, whether site content/assets are retained, or what happens on a second call despite idempotentHint being false.

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 with the action front-loaded and zero filler. The second sentence is terse to the point of being cryptic ('Needs key or sign-in'), but nothing is wasted.

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 2-parameter, destructive, no-output-schema tool, this is minimally adequate: annotations cover the safety profile and the description covers the outcome and auth. It falls short on what 'stop serving' leaves behind, whether the action can be undone, and how to identify the target site correctly.

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 0%, so the description must carry the parameter semantics and it largely doesn't. 'one of your sites' faintly implies 'name' identifies the site and 'Needs key' faintly implies the key param is a credential, but neither is stated, and there's no format, scope, or disambiguation guidance (e.g. is 'name' a hostname, a slug, or a display name?).

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 phrase plus resource: 'Stop serving one of your sites.' An agent immediately understands this takes a published site offline, and it's distinguishable from site_publish by the inverse operation. It doesn't name the sibling explicitly, so it's a 4 rather than 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?

Usage is implied by the operation itself (you call this when a site should no longer be served), and the description adds the auth prerequisite 'Needs key or sign-in.' But it never states when-not to use it, nor points to site_publish for the reverse operation or site_list for finding a site name.

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