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

The annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so safety profile is covered. The description adds nothing: it does not say that deletion is permanent, whether it can be undone, what happens to projects referencing the brand, or whether special permissions are needed. It only restates the mutation that the annotations already imply.

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?

It is one front-loaded sentence with no filler, restatement, or hedging. The problem is under-specification rather than verbosity; that is penalized in other dimensions, not here.

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?

This is a destructive mutation with no output schema and only partial parameter documentation. For this complexity, the description should at least state permanence, whether deletion cascades to projects, and what identifying value brandId expects. None of that is present.

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 only 50%: projectId is documented, but brandId is undocumented in both the schema and the description. The description does not explain brandId at all (for example, whether it is a saved-kit ID from list_brands or a project-scoped identifier), and it does not explain the interaction between brandId and projectId.

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 gives a specific verb and resource: 'Delete a saved brand kit.' That is enough to separate it from delete_bin, delete_project, delete_component, and delete_note, even though the description never names those siblings. The only gap is that it does not describe the scope of 'saved' (for example, whether the template is local or shared).

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 does not say when to use this tool rather than remove_font, delete_component, or list_brands/get_brand to check what is being removed. It also does not say whether deleting a brand kit affects projects that already use it through set_project_brand. Only the purpose is stated, so guidance is essentially missing.

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