create_items_batch_delete

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

The tool is clearly a batch delete operation (as implied by the endpoint and name), yet the annotations declare destructiveHint=false. The description itself says 'batch delete' but does not disclose that this permanently deletes items, nor does it mention any consequences, permissions, or reversibility. This contradicts the annotations, and the description fails to carry the burden of behavioral disclosure.

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 extremely short (two sentences), but it lacks a clear structure. It mixes a high-level phrase with an endpoint and a generic schema-reading instruction. While concise, it is under-specified and not front-loaded with the most important information (that this is a destructive batch delete).

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?

For a mutation/delete tool, the description is grossly incomplete. It does not specify what items are affected, what the request body must contain, what the response looks like (despite having an output schema), or any conditions or limitations. The annotation idempotentHint=true is not explained, and no guidance on idempotent retries is provided. An agent cannot safely invoke this tool without further investigation.

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 schema defines a single 'body' parameter as an open object with additionalProperties, and schema description coverage is 0%. The description only says to read the schema endpoint for expected fields, which is a pointer but not an explanation. It does not describe what the body should contain (e.g., list of item IDs) or any structure, leaving the agent without concrete parameter semantics.

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 'Create or act on batch delete' is vague and does not clarify that the tool performs a batch deletion of items. It does not distinguish from sibling tools like create_items_batch_update or delete_items_by_id. The name starts with 'create' which is misleading for a delete operation, and the description does not resolve this ambiguity.

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 such as delete_items_by_id or other batch operations. It only advises reading the schema for the request body, but does not explain the intended use case or prerequisites. No context about selecting this tool over other delete methods is given.

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