rollback_plan_get

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

No annotations provided; description states it is read-only and returns specific data (status, operation, parameters, caveats). Does not mention potential side effects or permissions, which are not expected for an inspection tool.

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: purpose, return values, and read-only clarification. 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?

Lists return fields despite no output schema, which helps agent understand expected data. Could include more detail on structure, but sufficient for common use.

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 schema already documents both parameters. Description adds no extra meaning 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?

Clearly states the tool inspects a reversal plan for an action_log entry, specifies the resource (STATE.json), the action (inspect), and lists return fields. Explicitly distinguishes from execution by stating 'Does not execute anything.'

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 indicates when to use (inspect before applying) versus executing via rollback_apply sibling. Lacks explicit prerequisites or exclusions, but context is sufficient.

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