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

No annotations are provided, so the description carries the full burden. 'Return' weakly implies a read operation, but the description does not disclose whether drills are generated or fetched, whether results are deterministic, how large the output is, or any auth/scoping constraints. For a tool with zero annotation coverage this is a significant gap.

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?

A single efficient sentence with the verb and resource front-loaded and no filler. It is well-sized, though its brevity is partly under-specification rather than disciplined trimming.

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?

An output schema exists, so return values need not be explained. However, with no annotations, no parameter documentation, and an ambiguous relationship to a very close sibling (red_team_replay_harness), the description is too thin for an agent to select and invoke this tool confidently.

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?

Three parameters (scenario_id, workflow_id, attack_family) have 0% schema description coverage and no elaboration in the description. The words 'remediation workflows' and 'adversarial drills' only loosely gesture at workflow_id and attack_family, leaving scenario_id and the relationship between the three filters unexplained.

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 ('Return') and resource ('adversarial drills') with a domain scoping ('agentic remediation workflows and MCP controls'). It is clear what the tool produces, but it does not differentiate itself from the near-identical sibling recipes_agentic_red_team_replay_harness or the other red-team-adjacent packs like recipes_agentic_threat_radar.

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 guidance, no condition that selects this tool over the replay harness or threat radar siblings, and no stated prerequisites. The agent must infer usage entirely from the tool name and the crowded sibling list.

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