migrate_pages_to_workers_guide

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

The description indicates a read-only, informational tool (a guide), but does not explicitly disclose behavioral traits like safety (non-destructive) or return format. With no annotations beyond a title, the description could add 'read-only' or 'no side effects' for full transparency.

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?

The description is a single, front-loaded sentence that directly states the action. It is concise and every word 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?

Given the tool has no parameters, no output schema, and a simple purpose (providing a guide), the description is largely complete. It could mention what the guide contains or how it is returned, but it is sufficient for an agent to understand the tool's function.

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 input schema has zero parameters, so there is nothing to document. By baseline, a tool with no parameters receives a 4. The description adds no parameter info, which is appropriate.

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 clearly states the tool's purpose: to provide a guide that should be read before migrating Pages projects to Workers. It specifies a specific verb ('read') and resource ('this guide'), and distinguishes itself from the sibling search tool by being a dedicated migration guide.

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 explicitly says 'ALWAYS read this guide before migrating Pages projects to Workers,' giving clear context for when to use the tool (before migration). It does not mention alternatives or when not to use it, but the directive is strong and unambiguous.

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