category_update

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

The description discloses that the update is partial, requiring at least one of name, slug, or parent_id. Annotations are consistent (idempotentHint=true) and the description adds context beyond structured fields.

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 two sentences, concise, and front-loaded with the verb and endpoint. No redundant information.

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 core purpose and update constraint but lacks details on return values, error conditions, or authentication requirements. With no output schema and 5 parameters, more context would improve completeness.

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%. The description lists three optional fields but does not explain required parameters site and category_id. It adds the partial update constraint but misses parameter-specific details like the minLength of name already in schema.

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 'Update a category' with the HTTP method and endpoint, and specifies the updatable fields (name, slug, parent_id). This distinguishes it from sibling tools like category_create and category_delete.

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 implies use for modifying an existing category but provides no explicit guidance on when to use this tool versus alternatives like category_create or category_delete. No exclusion criteria are mentioned.

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