Execute reviewed testimonial tasks

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

Goes well beyond the annotations (destructiveHint, non-idempotent) by disclosing exact failure semantics: stop on first failure, no retries, no rollback, no implicit continuation, and a return shape of known results plus failed index and unattempted indices. This is precisely the operational knowledge an agent needs before firing a destructive batch.

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 dense sentences, front-loaded with scope and then failure behavior; every clause carries operational weight. The opening is a noun fragment that reads telegraphically, but nothing is padded.

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 destructive, non-idempotent batch tool with no output schema, it covers scope limits, ordering, the confirmation gate, and the failure/return contract. It leaves the hash-mismatch path and interaction with the preview sibling implicit, which is the main remaining gap.

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 baseline is 3; the schema already documents tasks, account, confirm, and review_sha256. The description reinforces ordering and the pre-request hash gate but adds little syntax or per-parameter meaning beyond what the schema states.

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?

The description names the resource and scope precisely: a confirmed, ordered batch of one-to-twenty testimonial/import/invite tasks, executed with hash verification. It is distinguishable from the preview_testimonial_batch sibling by being the execution stage, though it never names that sibling explicitly.

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?

Usage is implied rather than stated: 'Confirmed' and 'verify exact hash before first request' suggest the tool must follow a preview/confirm flow, but the description never says to call preview_testimonial_batch first or what to do when the hash mismatches. No explicit when-not or alternative routing is given.

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