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

With no annotations provided, the description carries the full burden and does so well: it discloses permanence ('permanently'), the destructive nature, two distinct failure modes (linked transactions without a replacement, parent category with subcategories), and a required reassignment step. It stops short of describing permission requirements or what the response returns, keeping it from a 5.

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?

Three sentences, each earning its place: the action, the conditional prerequisite with its failure consequence, and the hard constraint plus confirmation guardrail. The core action is front-loaded in the first clause.

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?

No output schema or annotations exist, so the description must stand alone, and it covers action, prerequisites, failure modes, and a safety guardrail for a 2-parameter mutation. Minor gaps remain around permissions and side effects on the orphaned data once reassigned, but nothing needed to invoke it correctly is missing.

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 100%, so both parameters are already documented, giving a baseline of 3. The description goes beyond that by tying replaceWithCategoryId to its triggering condition and the consequence of omitting it (the call fails), which is semantic value the schema's terse 'Required when the category has transactions' only partially conveys.

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?

States a specific verb and resource ('Permanently delete a category by ID') with the scope qualifier 'permanently'. It is clearly distinguishable from sibling deletions like delete_budget, delete_tag, or delete_transaction, all of which target different resources.

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?

Gives an explicit precondition ('Only call when the user explicitly confirms deletion') and the exact condition under which the optional parameter becomes mandatory ('if the category has linked transactions you must supply replaceWithCategoryId'). It also names a hard when-not case: a parent category with subcategories cannot be deleted. No sibling tool offers category deletion, so no alternative needs naming.

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