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

Goes well beyond the readOnlyHint=false / destructiveHint=true annotations: it discloses partial-update semantics, the read-only behavior of integration-synced categories that will be refused, the unsupported de-nesting operation, and the explicit guarantee that product membership is untouched.

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?

Front-loaded with what the tool changes, then constraints. Every sentence carries a distinct, actionable constraint; nothing is filler despite the length.

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 mutation tool with no output schema, it covers partial updates, refusal conditions, and cross-tool boundaries, which is everything an agent needs to invoke it correctly.

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 67% and the description reinforces that categoryId must come from get_categories and is never a name, plus explains parentId's MOVE-only semantics. Image/description/name parameters get no additional semantics, but the key ambiguity is resolved.

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?

Starts with a concrete verb+resource pair and enumerates the exact mutable fields (name, description, image, parentId, sortOrder). It is unmistakably distinct from siblings like hub_create_category, hub_delete_category, and hub_reorder_categories.

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?

Explicitly states prerequisites (id from get_categories, never a name), partial-update behavior (only passed fields change), and two hard refusal cases (un-making a subcategory top-level, integration-synced categories). It also routes the agent away from product membership work to update_product with categoryIds.

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