delete_importlist_bulk

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

The description adds no behavioral detail beyond the annotations. It confirms deletion, but doesn't explain side effects, reversibility, or scope. The instruction to read GET/schema is about input, not behavior. Since annotations already declare destructiveHint=true and idempotentHint=true, the description contributes little to behavioral 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?

The description is terse and front-loaded with the purpose, then the endpoint, then the args. It avoids wasted words and is well-structured. However, it omits essential details, so while concise, it's not comprehensive.

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?

The description lacks crucial information about the body format and the semantics of bulk deletion. It relies on external references (GET/schema) to fill in gaps. While an output schema exists, the input requirements are not explained, making the tool difficult to use correctly without external discovery.

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 description identifies the body as a request payload and directs to schema, but with 0% schema coverage, this is insufficient. It doesn't describe the expected structure (e.g., list of IDs) or any constraints. The guidance to read the schema is a pointer, not a semantic explanation.

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 states 'Delete ImportList.' which is a clear verb and resource, but it fails to clarify the 'bulk' aspect, making it ambiguous whether it deletes multiple items or a single one. It also doesn't distinguish from the sibling delete_importlist_by_id, which is a single-item delete. The endpoint is provided but that's not purpose. It's a step above a tautology but lacks specificity.

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?

There is no guidance on when to use this tool versus alternatives like delete_importlist_by_id. It doesn't mention prerequisites, permissions, or the difference between bulk and single deletion. The only instruction is to read the GET/schema endpoint for the body, which is about parameter structure, not usage context.

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