deleteCustomCategories

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds no new behavioral details, such as whether deletion is permanent, whether it cascades to other data, or what happens if categories do not exist. Minimal added value beyond annotations.

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 very short (three words), which is concise but at the expense of completeness. While not verbose, it sacrifices necessary context. A better structure would include at least a brief sentence covering the parameters.

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 simple delete tool with two required parameters and no output schema, the description should cover the purpose of each parameter and any constraints. It does not, leaving the agent underinformed. Given the tool's simplicity, a short but complete description is expected.

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 coverage is 0% (no parameter descriptions). The description does not explain the meaning of the 'categories' array or the 'type' enum. It fails to compensate for the lack of schema documentation, leaving agents to guess 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?

Description clearly states verb and resource: 'Delete custom categories'. It distinguishes from sibling tools like 'createCustomCategories' and 'getCustomCategories' by indicating a delete operation. However, it could be more specific about the deletion criteria (by name and type) which is evident only from the schema.

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 on when to use this tool versus alternatives such as 'deleteTransaction' or 'deleteRecurringTransaction'. An explicit when-to-use or when-not-to-use would help an agent select the correct tool.

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