alterios_fast_live_bulk_delete

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

Only mentions 'destructively delete' and 'dangerous workflow' but lacks details on irreversibility, side effects, confirmation steps, or how the plan workflow differs from direct deletion. With no annotations, more transparency is expected.

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 single sentence is too concise for the tool's complexity. It lacks structure (e.g., separating plan vs delete modes) and fails to convey essential information without being verbose.

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?

With 20 parameters, nested objects, and an output schema, the description is drastically under-specified. It provides no context on the workflow, safety checks, or how to integrate with sibling tools, leaving the agent with almost no actionable 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?

Schema description coverage is 0% and the description provides no information about any of the 20 parameters (8 required). Parameters like selected_content_ids, expected_count, and delivery_evidence are left entirely unexplained.

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 identifies the tool's action: 'destructively delete' or 'plan' for 'explicitly reviewed content rows'. It distinguishes from siblings like alterios_delete_user and alterios_delete_role by specifying content rows and a dedicated dangerous workflow.

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?

No guidance on when to use this tool versus siblings, or when to plan vs execute. Does not explain prerequisites or safety measures despite being a destructive tool.

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