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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Return' suggests a read-only lookup, but the name 'harness' implies potentially more complex behavior, and the description does not clarify side effects, required context, failure modes, or what distinguishes a replay fixture from a live drill.

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?

The description is a single compact sentence with no wasted words and front-loads the primary output types. It is concise, though the brevity contributes to under-specification in other dimensions.

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?

The tool has five optional but undocumented parameters, no annotations, and a large sibling set; the description does not explain how filters interact, what a valid call looks like, or what kinds of replay fixtures the agent should expect. The output schema helps, but the description leaves too much unspecified for reliable selection and invocation.

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%, so the description must compensate by explaining how parameters such as severity, replay_id, scenario_id, workflow_id, and attack_family relate to the returned fixtures. It does not mention any of these parameters, leaving the agent to guess their meanings from names alone.

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 clearly states a specific action ('Return') and a specific resource ('replay fixtures, expected decisions, and evidence gates for red-team drills'). This is specific enough to distinguish it from sibling tools like recipes_agentic_red_team_drill_pack, though it does not explicitly name or contrast those siblings.

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?

The description implies the tool is for red-team drill replay scenarios, but it gives no guidance on when to prefer this over the many sibling recipe tools, nor any when-not-to-use conditions or alternatives. The agent must infer usage from the name and context rather than from explicit direction.

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