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

Annotations already declare the safety profile (destructiveHint=false, idempotentHint=true), and 'Categories are never deleted from here' is consistent with that, adding a little clarity about non-destructive archiving. Beyond that it discloses nothing new such as what happens to a category's transactions when archived, whether archived categories remain visible, or any permission requirements.

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 leading sentence is well front-loaded and earns its place, but the two trailing sentences about integer minor units and YYYY-MM-DD/YYYY-MM date formats describe conventions for tools that take amount or date parameters — this tool has none, so that text is dead weight for the agent calling update_category.

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 six-parameter mutation with no output schema, the essentials are roughly covered and annotations handle safety, but the description omits the id/sort semantics and the consequences of archiving a category, while spending its tail on amount/date conventions that do not apply here.

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?

With 0% schema description coverage, the description must carry parameter meaning. It covers name, icon, color, and archived (including the archived: true syntax), but never explains the required id or the sort field, leaving two of six parameters undocumented anywhere.

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 first sentence gives a precise verb-plus-resource with the exact editable fields: rename, change icon or color, or archive. It also explicitly bounds the tool's scope ('Categories are never deleted from here'), which cleanly separates it from create_category and any delete-style sibling.

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 implies usage clearly: mutations are limited to rename/icon/color/archive, and deletion is not available here, so the archive flag is the intended alternative to deleting. It stops short of explicitly naming an alternative tool or stating prerequisites, so it does not reach full when/when-not coverage.

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