rename

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

Annotations already mark this as destructive and non-idempotent, and the description meaningfully adds behavioral guidance beyond them: reuse returned Page Snapshots and receipts, and avoid read/list verification. This is exactly the kind of operational nuance an agent needs and cannot infer from the schema alone.

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 compact sentences with no filler. The purpose is front-loaded, and the second sentence delivers critical post-action guidance. Every clause 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 annotations, rich input schema, and output schema, the description covers the essential contract: what the tool does, the snapshot requirement, per-page limits, and post-call behavior. It could slightly improve by contrasting with the 'move' sibling, but nothing critical is missing.

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%, so the baseline is 3. The description adds useful semantic context by saying 'one operation per page' and connecting the operation to 'latest Page Snapshots,' which clarifies how to construct operations and use if_version, though the individual parameter details are already well documented in the schema.

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 a specific action ('Rename dynamic pages') and the resource type, with a distinguishing mechanism ('using latest Page Snapshots'). It also imposes a clear scope ('one operation per page'), making the tool's purpose unambiguous.

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 gives clear operational context: use the latest Page Snapshots, and after a successful rename do not verify via read or list. It does not explicitly compare this tool to siblings like move or update, so it falls short of a full when-to-use-vs-alternatives explanation.

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