delete_cart_transform

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

The description only says 'Delete a cart transform' with no annotations to rely on. It fails to disclose whether deletion is permanent, what happens if the transform does not exist, or any permissions required, which is critical for a mutating operation.

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 one short sentence with no fluff, earning a high score for brevity. However, it is so minimal that it misses opportunities to include valuable usage or behavior details.

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 a simple delete operation with one parameter and no output schema, the description is not fully complete. It omits any mention of side effects, failure modes, or prerequisites, making it less useful than expected for a mutating tool with no annotations.

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 input schema documents the single 'id' parameter with the description 'Cart Transform ID to delete,' providing full coverage. The tool description adds no additional parameter meaning beyond this.

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 'Delete a cart transform' clearly states the verb (delete) and resource (cart transform), distinguishing it from sibling tools like get_cart_transforms, create_cart_transform, and update_cart_transform. However, it lacks any additional context about the delete operation's scope or consequences, so it is clear but not exceptional.

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 usage guidance is provided. The description does not mention when to use this tool versus other cart transform operations, nor does it specify any prerequisites or exclusions.

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