list_attack_strategies

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

No annotations so description carries full burden. It clearly states this is a discovery-only, read-only operation. While it doesn't elaborate on authentication or side effects, the simplicity of a list tool makes this sufficient.

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 short, informative sentences. The first sentence states the purpose directly. No extraneous information.

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 zero-parameter tool with an output schema, the description is complete: it explains the tool's purpose and usage context without missing any critical information.

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?

No parameters in the input schema, and description adds no parameter details (not needed). Baseline 4 for zero parameters.

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 'List available PyRIT attack strategies and their constructor parameters' which is a specific verb (list) and resource (attack strategies). It distinguishes from sibling tools like run_attack or cancel_attack that perform different actions.

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 explicitly states 'Discovery only -- this does not recommend or select a strategy. The calling agent must choose which attack to run based on its own plan.' This provides clear when-to-use and when-not-to-use guidance, and mentions the agent's responsibility.

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