update_category

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

Annotations already indicate readOnly=false, destructive=false, and idempotent=false. The 'partial' qualifier adds meaningful behavioral context beyond annotations, signaling that only provided fields are updated and omitted fields are left unchanged. No further side effects or auth requirements are disclosed, but the partial hint is valuable.

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 that conveys the essential purpose and partial-update semantics without any redundant words. It is appropriately concise for the tool's evident simplicity.

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?

With 7 parameters, 1 required, and no output schema, the description is too sparse to fully inform an agent. It lacks parameter semantics, any mention of response behavior, and fails to distinguish usage from sibling update tools. The partial update hint is helpful but insufficient for complete understanding.

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 0%, so the description must compensate. It only mentions categoryId as the identifier, but gives no meaning or usage for the other six parameters (name, image, status, parentId, sortOrder, description). Field names are self-evident, but constraints, relationships, and allowed values are undocumented.

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 verb 'Update', the resource 'category', and the lookup mechanism 'by categoryId'. The qualifier 'partial' distinguishes it from a full replace operation and from create_category, its most obvious 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?

Usage is implied: use when you need to modify an existing category. However, there is no explicit guidance on when to prefer this tool over create_category or update_product, nor any exclusions or prerequisites beyond providing categoryId.

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