update_category

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

The description discloses key behavioral traits: updating properties, the special child replacement for groups, and the prohibition on conversion. The idempotentHint annotation is consistent with update operations, and the description adds value beyond the annotation by clarifying the group-specific behavior.

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 concise with three sentences, no unnecessary words, and front-loads the core purpose. Every sentence adds value.

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 tool's complexity (9 parameters, special group behavior), the description covers the most critical points: conversion prohibition and child replacement. However, it lacks information about return values or error handling. Since there is no output schema, a brief note on success response 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 56%, so some parameters are already documented in the schema. The description adds valuable context for the 'children' parameter (explaining replacement for groups), but does not elaborate on other parameters like 'is_income' or 'exclude_from_budget'. This adds some but not full compensation.

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 it updates properties for an existing category or category group, and explicitly distinguishes between the two types, including the special behavior for category groups (replacing children). It also states what cannot be done (conversion), which helps differentiate from siblings 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 description provides clear context on when to use (update existing category/group) and the specific behavior for groups. However, it does not explicitly mention alternatives or when not to use it, though the naming and sibling list imply its role.

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