Threat Simulations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully disclosed. The description adds valuable context beyond annotations by noting the playbooks are 'step-by-step commands by platform for safely reproducing behavior in a lab' — telegraphing the safe, non-production execution context and platform-specific content. This meaningfully enriches what annotations provide.

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 sentences, zero filler. The first sentence states the purpose, and the second states the use case. Every clause earns its place — no redundancy, no vague marketing language.

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 single-parameter, read-only retrieval tool with a full output schema and complete annotation coverage, the description is fully complete. It explains what the output contains (step-by-step commands by platform), the safety context (lab reproduction), and the intended operational purpose (detection testing). Nothing material is missing for an agent to choose and invoke this tool correctly.

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 coverage is 100% with the single required threat_id parameter documented. The description clarifies that the parameter identifies 'a specific threat,' aligning with the example format. With full coverage and a single required param, the schema carries most of the weight; the description adds the context that the ID references a threat the playbooks are attached to, providing adequate framing beyond the schema.

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 uses 'Get the adversary-emulation / simulation playbooks attached to a threat' — a specific verb (get) plus a specific resource (adversary-emulation playbooks) tied to a threat. It clearly distinguishes from siblings: list_simulations is a broad catalog, while get_threat_hunting_bundle is hunting-focused; this tool is explicitly simulation/emulation playbooks for a specific threat, differentiating it well.

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 states when to use: 'to operationalize detection testing for a specific threat' and frames the output as 'safely reproducing the behavior in a lab'. It implies this is for lab/detection-testing scenarios. It doesn't explicitly name alternatives or exclusions, but the context is clear enough given the specific-purpose framing.

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