find_defense_evasion

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether the tool performs read-only operations, requires authentication, or modifies state. The list of techniques implies searching but offers no details about output format, side effects, or limitations.

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 concise—a single sentence with a dash-separated list. It is efficiently front-loaded with the core purpose. While brief, it avoids fluff. A structured breakdown of technique groups would improve scannability, but the current form is adequate.

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?

Given the tool has 4 parameters, no output schema, and no annotations, the description should clarify what the tool returns (e.g., technique names, commands, references). It only lists technique categories, leaving critical gaps about output format, pagination, or dependencies like environment_id.

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?

The input schema already fully describes all 4 parameters with 100% coverage (including enum values for evasion_type). The tool description merely repeats the technique names without adding semantic nuance or usage examples, so it adds no value 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 explicitly states 'Find defense evasion techniques' and lists representative examples (EDR bypass, AMSI bypass, etc.), making the tool's overall purpose clear. However, it does not differentiate from sibling tools that focus on specific evasion subtypes like find_dll_hijack, leaving some ambiguity for agents choosing among related tools.

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 provides no guidance on when to use this tool versus alternatives (e.g., find_dll_hijack, find_token_abuse). There is no mention of prerequisites, recommended scenarios, or exclusions, leaving the agent without decision support for tool selection.

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