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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safe, offline, non-mutating nature is fully covered by structured data. The description adds the subject matter of the guide, which helps the agent decide whether to invoke it, but discloses nothing further about behavior—no indication of length, format, or whether it must precede other calls.

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?

A single front-loaded sentence with the imperative first and the covered topics after it. Every clause carries information; nothing is padded or repeated from the title.

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 zero-parameter reference tool with read-only annotations and no output schema, the description gives the agent enough to know what it will learn and to place it before construction work. A note on what it returns (prose documentation vs. structured data) would close the remaining gap, but it is minor.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is trivially complete.

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 the resource (a guide) and enumerates the exact topics it covers: pages, forms, the built-in database, publishing, and credits. That is enough to separate it from the action-oriented siblings like write_page, publish_site, or query_records, though the framing is a directive ('Read this first') rather than a crisp statement of what the tool returns.

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?

'Read this first' gives an explicit sequencing instruction relative to the other tools, which is the key usage signal for a documentation tool. It stops short of stating when the agent should re-read it or what to do if it already has the information, so it is clear context rather than full when/when-not guidance.

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