update_inventory_category

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

Annotations indicate idempotentHint=true and not destructive. The description adds behavioral context about validation (rejects duplicate names and self/descendant moves), which goes beyond annotations. No contradiction found.

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 description is three sentences, each essential. It front-loads the main action and then adds usage constraints and rejection rules. Every sentence earns its place without redundancy.

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?

Given the presence of an output schema, return values need not be explained. Parameters are fully covered in context, and constraints are clearly stated. The description is complete for an update tool with moderate complexity.

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?

Although schema coverage is 100%, the schema descriptions are generic ('a string that will be trimmed'). The tool description adds meaning: category accepts ID or exact name, parentCategory disambiguates duplicates, newParentCategory is for moving. This compensates for the schema's lack of semantic detail.

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 description clearly states the tool's purpose as renaming and/or moving an inventory category, with specific verb-resource pairing. It distinguishes from siblings like create_inventory_category and delete_inventory_category.

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 provides explicit guidance on when to use parentCategory (when name may be duplicated) and notes constraints like rejecting duplicate names and self/descendant moves. While it doesn't explicitly state when not to use this tool, the context is clear for a specific update operation.

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