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

Goes well past the annotations: debits every shot at once atomically, queues in parallel, server checks each shot then assembles/edits/delivers in conversation, failed shots are auto-refunded, and the request is rejected before any charge if English directions are missing. These are exactly the credit-safety and failure-mode facts an agent needs and that readOnlyHint=false / destructiveHint=false do not convey.

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?

Front-loaded with the atomic-charge and delivery behavior, then preconditions, then failure/retry rules — a sensible order with no filler. The trailing pasted argument JSON restates the schema shape and is the one portion that could be dropped.

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 charging, multi-object, nested-payload tool with no output schema, the description covers authorization (confirmed/rights_confirmed), cost (max_credits equals the shown total), refusal conditions, idempotent retry, refunds, and where the result appears. Nothing essential for a correct invocation is missing.

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?

Top-level schema coverage is low and path/body carry no descriptions, but the description supplies real semantics: confirmed must follow user approval of the displayed total, max_credits must equal that total, idempotency_key is for safe retry after timeout, english is keyed per shot number. It does not mention quality or resolution, though those are documented inside the schema, so it stops short of full coverage.

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 — accepting an entire multi-shot plan in one atomic confirmation — and immediately distinguishes it from the per-shot generate path and from kelpo_get_shoot, which is referenced as the prerequisite lister. An agent can tell exactly what this does and what it is not.

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?

Gives concrete preconditions and alternatives: only after the user approved the displayed total with confirmed=true, reuse the same idempotency_key on timeout, and if kelpo_get_shoot reports english_directions_needed the call is refused unless english is supplied. It also routes the rights check to the same rule as generate (rights_confirmed), so the when/when-not logic is explicit.

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