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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds useful context that the output is instructional content spanning three CDNs plus a WordPress path, but it does not say what form the instructions take or whether they are step-by-step, code snippets, or links.

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 well-built sentences, front-loaded with what the resource is and what it covers. The terminal-avoidance clause about the WordPress plugin is mild flavor but justifies its inclusion by explaining that path.

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 read-only instruction-retrieval tool with one optional enum param fully documented in the schema, the description is nearly complete. A hint about the returned artifact (format/length) would close the last gap, especially with no output schema.

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% — the single 'cdn' enum parameter is fully documented in the schema, including that omission returns all three options. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 names a specific resource (Sulvo Boost setup instructions) and enumerates its coverage (Cloudflare, AWS, Fastly, WordPress plugin), so an agent knows exactly what it retrieves. It does not, however, distinguish itself from the close sibling get_sulvo_installation_instructions, leaving overlap ambiguity.

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?

Coverage of the CDN options implies when the tool is relevant (setting up Boost), but there is no explicit when-to-use or when-not statement. Critically, it never clarifies its relationship to get_sulvo_installation_instructions, which an agent could easily pick instead.

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