migrate_pages_to_workers_guide

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

Annotations already declare readOnlyHint=true. Description confirms a read operation ('read this guide') but adds no additional behavioral details such as what the guide contains, format, or prerequisites. With annotations covering safety, score is adequate.

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 imperative instruction. No wasted words.

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 read-only guide retrieval tool with no parameters, description sufficiently conveys purpose and usage. No output schema needed. Contextually complete given tool simplicity.

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?

No parameters in schema, so description correctly has no parameter info. Baseline of 4 is appropriate as no param details are needed.

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?

Description clearly states the tool provides a guide for migrating Pages projects to Workers. However, it uses 'read this guide' rather than an explicit verb like 'get' or 'retrieve'. Distinguishes from sibling tool search_cloudflare_documentation by specifying a particular migration context.

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?

Explicitly says 'ALWAYS read this guide before migrating Pages projects to Workers', providing clear context on when to use. No explicit exclusions or alternatives, but the strong recommendation implies proper usage sequence.

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