rollback_infrastructure_changes

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

No annotations are provided, so the description carries full burden. 'Rollback' implies a destructive mutation, but the description doesn't disclose critical behaviors: whether it's reversible, what permissions are needed, potential downtime, or rate limits. It mentions 'recent' but doesn't define timeframe.

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?

Extremely concise with a single, front-loaded sentence. No wasted words or redundant information, making it easy to parse quickly.

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 destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't cover behavioral risks, prerequisites (e.g., backup must exist), or expected outcomes. Given the complexity implied by 4 parameters including scoping options, more context is needed.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds no additional meaning beyond implying 'recent' changes, which loosely relates to 'backup_id' but isn't explicit. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Rollback recent infrastructure changes' states the general purpose but lacks specificity about what infrastructure or changes are involved. It doesn't distinguish from sibling tools like 'create_infrastructure_backup' or 'validate_infrastructure_changes' beyond the basic verb 'rollback' versus 'create' or 'validate'.

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?

No guidance on when to use this tool versus alternatives like 'validate_infrastructure_changes' or 'create_infrastructure_backup'. The description implies it's for undoing changes, but doesn't specify prerequisites (e.g., requires a backup) or exclusions (e.g., not for minor config updates).

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