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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine context beyond them: determinism, that it produces a recipe rather than executing anything, that it must be reviewed/saved before admission, and that large outputs should go through the CLI continuation instead of flooding agent context.

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 core operation, then mechanism, then exclusions. Five sentences, each carrying information, with no filler; slightly dense but well ordered.

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 tool with a very large nested recipe schema and no output schema, the description conveys the essential role, non-effects, and next step (review/save recipe) adequately. It leaves the deep recipe structure undocumented, but that is largely a schema concern.

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 0% across 5 parameters, so the description must compensate. It explains 'axes' (JSON Pointer paths relative to each scenario input) and 'selection' (matrix expands all combinations, seeded sample selects count cases), but says nothing about projectId, environmentId, or the structure of the large 'recipe' object, leaving significant gaps.

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 states a specific verb and resource ('Prepare a deterministic explicit case population') and explains the mechanism (JSON Pointer axes expanded by matrix or seeded sample). This is clear enough to distinguish it from a validation or run tool, though it never names the sibling alternatives it differs from.

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?

It gives explicit exclusions — 'Does not run a target, allocate services, save scenarios or assess results' — which routes the agent away from batch/run/save/assess siblings, and adds workflow guidance ('Review/save the returned recipe before admission', use CLI continuation for large recipes). No sibling is named by name, but the when/when-not context is clear.

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