delete_brands

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

With no annotations, the description carries full responsibility for disclosing behavior. 'Delete' implies a destructive mutation, but it does not mention irreversibility, required permissions, cascading effects, or the behavior of the dry_run parameter. The tool could delete data permanently without any warning.

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 and front-loaded, but it is under-specified rather than appropriately concise. It states the core action but omits essential usage details, so the brevity negatively impacts usefulness.

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 destructive tool with no annotations and no output schema, the description is not complete enough. It fails to mention the purpose of dry_run, which is a critical safety mechanism, and provides no context about what happens after deletion or how to verify the operation.

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 adds no information about the parameters global_key, brand_ids, or dry_run. It does not explain that dry_run is a preview mode, that brand_ids accepts multiple IDs, or how global_key relates to scoping.

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 uses a specific verb 'Delete' with the resource 'brands' and the method 'by ID'. This clearly states what the tool does and differentiates it from sibling tools like list_brands, create_brand, and update_brand.

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 is provided about when to use this tool versus alternatives, prerequisites, or safety considerations. Given that this is a destructive operation, it should explicitly mention using dry_run for previewing, but it does not.

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