Update a category group

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description adds genuinely non-obvious behavior: hiding a group cascades to every category inside it and surfaces in list_categories as hidden. It also clarifies PATCH-style partial-update semantics. It omits any auth/permission notes, keeping it just short of 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 tight sentences, front-loaded with the two supported operations, then update semantics, then the cascade warning. No filler or repetition.

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?

A three-parameter mutation tool with no output schema and full annotation coverage: the description covers operations, partial-update behavior, cascade side effects, and the correct recovery path. Nothing an agent needs to call 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 description coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the downstream consequence of the `hidden` parameter (all child categories reported hidden, and the group is the correct place to reverse it) and by restating partial-update 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?

States a specific verb+resource ('Rename a category group or hide/unhide it') and immediately scopes what changes ('Only the fields you pass are changed'). It is clearly distinguishable from sibling tools like update_category and create_category_group.

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 explicit guidance for the hide/unhide case and names the alternative behavior ('unhide the group here rather than trying to unhide them one by one'). It doesn't state when to prefer this over update_category, but the resource boundary is unambiguous.

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