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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds material context beyond them: deferred execution behind a human approval gate, configurable MCP approval requirements, and that business workflow approvals always apply. It stops short of saying what happens to budget line items that reference the deleted category, or whether deletion fails when the category is in use.

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 action is front-loaded in sentence two, and the approval mechanics are concise. The opening sentence about RetailHardHat budgets records is filler that duplicates scope already implied by the tool name and can be dropped.

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?

The output schema exists, so return values need no explanation, and the approval gating is well documented. However, for a destructive tool the description omits key operational facts: referential impact on budget line items, failure modes when the category is in use, and how to source the categoryId.

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 single parameter categoryId has 0% schema description coverage, and the description does not compensate. It never says that the id is a UUID, where to obtain it (list_budget_categories), or how a custom category id differs from a standard one. Only the phrase "custom budget category" hints at what the id points to.

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 second sentence gives a specific verb and resource: "Remove a custom budget category." That distinguishes it from update_budget_category and from bulk deletes like delete_budget or delete_budget_line_item. The opening sentence about RetailHardHat budgets records adds scope but is near-boilerplate.

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?

It names the required prerequisite sequence: no change happens until a human approves in Settings > MCP and execute_approved_action is called, which tells the agent this is not a direct-execute tool. It does not name alternative tools such as update_budget_category or explain the when-not case, such as when the category is still in use.

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