remove_attacker

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

Discloses multiple behavioral traits: soft-delete, version creation, ID preservation, linked CO tombstoning, and read-time derivation of orphaned controls. No annotations exist, so description fully covers transparency.

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?

Three concise sentences: purpose, lifecycle details, and restoration reference. Front-loaded and no wasted text.

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?

Tool has output schema, so return values are covered. Description explains soft-delete mechanics and reverse operation. Advanced context like prerequisites is implied and not critical for a deletion tool with documented schema.

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?

Input schema covers model_id and attacker_id descriptions (67% coverage). Description adds no new parameter insight beyond schema. Baseline 3 applies due to high schema coverage.

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?

Clearly states 'Soft-delete an attacker' with verb and resource. References similar lifecycle to remove_asset and restoration via restore_attacker, distinguishing it from 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?

Provides context by referencing similar lifecycle to remove_asset and explicitly mentions restore_attacker for undo. Does not exclude other deletion tools but given the sibling list, the name and description sufficiently indicate its specific purpose.

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