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

Goes well beyond the annotations: it discloses credit spend at prismposter.com parity, the approval/consent gate for price thresholds, real people, and licensing, plus where outputs land. The refusal policy for minors, public figures, and office holders is stated as pre-charge, which an agent cannot infer from readOnlyHint=false / destructiveHint=false alone.

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?

Capabilities are front-loaded in the first sentence and each later sentence carries real information (cost, approval gate, storage, refusals). It is longer than typical but not padded; minor tightening is possible in the approval sentence.

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 7-parameter generative mutation with billing, consent, and refund-policy implications, it covers the decisive unknowns: who pays, what blocks execution, what happens to the output. Only the shape of a successful response (job id vs URL) is left implicit, which is expected given there is no output schema.

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 every parameter including approval_id and idempotency_key is already documented, setting the baseline at 3. The description adds only light cross-parameter framing (edit vs upscale, approval resumes the approved job), not syntax or new semantics.

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?

Names a specific verb and resource plus the full capability envelope (background replace, object add/remove, restyle, in-image text, 2x/4x upscale). It is clearly separable from create_image (creates from nothing) and upscale_video (video, not pictures) in the sibling list.

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?

States the routing rule for cost (quote_job prices it first, free) and the branch where approval_required is returned before anything runs. It does not explicitly say when to prefer a sibling like create_image or open_in_editor, but the context needed to choose correctly is present.

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