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

No annotations exist, so the description carries the full behavioral burden. 'Return' implies a read operation, but it says nothing about whether results are static fixtures or generated, whether filtering combines across the five optional parameters, or whether authentication or drill state is required to get meaningful output.

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 compact sentence with the returned artifacts front-loaded and no filler. It is efficiently structured, though its brevity is achieved partly by omitting necessary detail rather than by disciplined editing.

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-value description is not required, but the tool has five undocumented filter parameters, zero annotations, and no usage context. For a five-parameter retrieval harness, the definition leaves the agent without enough to invoke it correctly or interpret what the filters do.

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?

Five parameters (severity, replay_id, scenario_id, workflow_id, attack_family) all have 0% schema description coverage, no enums, and nullable defaults, yet the description mentions none of them or how they filter the returned fixtures. This is the same failure mode as the LOW calibration case and leaves every parameter's meaning to guesswork.

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 a specific verb ('Return') and three concrete artifacts (replay fixtures, expected decisions, evidence gates) scoped to red-team drills, which an agent can distinguish from the similarly named recipes_agentic_red_team_drill_pack. It is clear but stops short of explicitly differentiating itself from that sibling.

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, when-not-to-use, or prerequisite guidance. The obvious alternative, recipes_agentic_red_team_drill_pack, is never mentioned, so an agent has no basis for choosing between them.

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