update_category

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

Given the idempotentHint annotation, the description's statement 'Only include fields you want to change' adds concrete behavioral detail that unspecified fields remain unchanged—valuable context beyond the annotation.

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 a single, front-loaded sentence with no filler words; every element from the verb to the partial-update instruction is essential.

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?

The description covers the tool's purpose, key usage guidance, and field list. Combined with full schema documentation and annotations, it provides sufficient context for an agent to select and invoke the tool correctly, though it omits return-value behavior.

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?

All 7 parameters are fully described in the schema, so the description mainly needs to add usage semantics; it does so by emphasizing that only desired fields should be passed, reinforcing the schema's optionality.

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 names a specific verb ('Update') and resource ('a category'), and lists the specific fields (name, slug, parent, description, image), making it distinct from sibling tools like create_category or delete_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 phrase 'Only include fields you want to change' provides clear guidance on how to perform partial updates, which is a key usage point for this tool. It implies the tool is for modifying existing categories, distinguishing it from creation and deletion tools.

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