Retry failed batch photos

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

Adds substantial behavior beyond annotations: preview_id expires after 10 minutes and is usable once, requeued photos are charged when processed, and the preview exposes exact per-photo and estimated credit costs. This gives the agent the safety and cost context needed before committing a mutation.

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?

The description is front-loaded with the core action and then explains the two-step flow, user confirmation, and cost in a compact sequence. Every sentence supports correct invocation, with no wasted filler.

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 the critical preview workflow, preview_id constraints, and pricing well enough for a two-step mutation tool. Because there is no output schema, it could be more complete about what execute=true returns after requeueing, but the essential invocation details are present.

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 schema already documents all seven parameters. The description still adds meaningful workflow semantics for execute and preview_id, including preview validity and one-time use, though it does not elaborate on limit, date filters, or stagger_seconds beyond 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?

States a specific verb and resource: retry failed batch photos for a given reason. The two-step preview/execute framing makes its purpose distinct from sibling tools like submit_batch or get_batch_photos.

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?

Explicitly instructs the agent to call first with execute=false, show the preview to the user, then call again with execute=true and the preview_id. It does not compare against alternative remediation tools, but the workflow guidance is clear enough to select and invoke it correctly.

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