Review exact ordered subscriber tasks

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context on top: it is purely local, performs SHA-256, and explicitly touches no provider, no key, no identity check. It stops short of explaining what the digest is used for or what the preview returns.

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?

Two tight sentences that lead with the action and follow with the boundary list. Dense jargon ('selected profile label and reviewed schema') costs a little readability, 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 read-only preview tool with full schema coverage this is adequate, but it omits the one thing the agent most needs: that this is the pre-flight for submit_subscriber_batch and what to do with the SHA-256 result. With no output schema, the return value's role goes unexplained.

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 description coverage is 100%, so both parameters are already documented, including the ordering, the 'exact native arguments' note, and the 1-20 maxItems clarification. The description restates 'exact ordered... work' and 'selected profile label' without adding syntax or new constraint detail, so baseline 3 applies.

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: 'Local validation and SHA-256 of exact ordered subscriber/segment/workflow/custom-field work'. An agent can tell this is a dry-run validation pass, not an executor. It does not, however, name the sibling submit_subscriber_batch it obviously pairs with, so sibling differentiation is only implied by the schema's tool enum.

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?

There is no when-to-use or when-not guidance and no routing to the alternative. The negative clauses ('No provider reads, key load...') imply a safe pre-flight step, but the agent is never told this precedes submit_subscriber_batch or that the same tasks should be submitted on success.

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