Delete Action Sets Bulk

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

Annotations already mark destructiveHint: true and idempotentHint: true. Description adds atomicity and reconstructability via re-uploading CSV, which provides helpful context beyond annotations without contradiction.

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, front-loaded with action and constraints. Every word conveys necessary information with no redundancy.

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's complexity (bulk, atomic, destructive), the description covers core behavior and safety. Missing details like partial failure behavior are mitigated by output schema existence and atomicity claim.

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 0%. Description only mentions 'action_set_ids' as 'by ID' and completely omits any explanation of 'request_id' parameter, leaving a significant gap for the agent to understand its purpose.

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?

Description clearly states verb 'Delete', resource 'vulnerability remediation action sets', and scope 'multiple by ID (up to 100) in one atomic call', distinguishing it from sibling 'delete_action_set' which is singular.

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?

Description implies usage for bulk deletion with 'up to 100' and 'atomic call', but does not explicitly state when to use this vs the singular alternative 'delete_action_set' or provide exclusions.

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