rollback_operation

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

No annotations provided, so description must carry full burden. It indicates destructive action ('Reverse', 'restores entity') but does not disclose required permissions, irreversibility, error handling for invalid auditEntryId, or what happens to dependent operations.

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, well-structured sentence that efficiently conveys the tool's purpose and mechanism. No unnecessary 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, single-parameter tool, description adequately covers core behavior and parameter meaning. However, could briefly mention reversible/irreversible nature or dependencies, but not critical given 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?

Schema already describes auditEntryId as 'ID of the audit entry to reverse'. The description adds context by explaining the effect ('restores entity to before-snapshot') and reinforces the parameter's role, adding value beyond 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?

Description uses specific verb 'Reverse' and clear resource 'specific committed operation via audit entry ID', with added context of restoring entity to before-snapshot. This distinguishes from sibling tools, none of which describe similar rollback functionality.

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?

Implies usage for reversing committed operations via audit entry ID, but no explicit when, when-not, or alternative tools. Context is clear but lacks explicit guidance.

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