rollback_prompt

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

Discloses key behaviors: toggling between versions on repeated rollback, 409 errors for first deployment or deleted previous version, and Pro+ requirement. No annotation provided, so description carries full burden and does well.

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?

Three concise sentences covering purpose, error conditions, and toggle behavior. No redundant information. Every sentence 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?

Covers behavior, errors, and toggle effect. Missing any example or mention of return value (no output schema). Fairly complete for a rollback tool.

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 provides both parameter names and descriptions with 100% coverage. Description adds no additional meaning beyond schema. Baseline of 3 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?

Description clearly states tool reverts a deployed prompt to previous version, specifying verb (revert), resource (prompt deployed to label), and adds detail about versioning and toggle behavior. Distinguishes from siblings like deploy_prompt.

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?

Implicitly clear when to use (to undo a deployment), but lacks explicit guidance on when not to use or comparison to alternatives. No exclusions or alternatives mentioned.

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