Delete custom categories.

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

Annotations already carry destructiveHint=true and idempotentHint=false, so the agent knows this is a destructive write. However, the description adds no behavioral context beyond the bare word 'delete' — e.g., whether deleting a category affects existing transactions, whether built-in categories are excluded, or what happens when two of the same category are provided.

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 only one short sentence, but this is under-specification rather than conciseness. No content earns its place, so nothing is front-loaded; it is simply the name restated.

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 two required parameters and no output schema, the description is incomplete: it does not describe what gets permanently deleted, whether deletion is scoped by account or category type, or how success/failure of the operation is conveyed. An agent could call it tentatively, but important edge behavior is absent.

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%, yet the description makes no effort to explain the two required parameters. The enum values (expense/income/investment) and the 'categories' array are self-descriptive in the schema, which keeps this from being a 1, but the description itself adds no meaning for the `type` discriminator or the category name strings.

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 custom categories' verbatim restates the title and the tool's own name, adding no new information. It names a verb and resource, but because it is a pure tautology of the title it does not differentiate or clarify beyond what the agent already sees in the tool name.

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 given about when to use this tool versus alternatives. Siblings such as getCustomCategories, getCategoriesByType, and createCustomCategories exist, but the description does not mention them, nor any conditions that should trigger deletion, prerequisites, or consequences.

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