Bestellstatus aktualisieren

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action ('updates the status') without revealing side effects, permission requirements, whether the note is appended or replaces existing notes, or any irreversible consequences. This is insufficient for a mutation tool.

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 short sentence that is efficient and front-loaded, with no wasted words. It could be more informative, but conciseness is not about completeness; it earns a 4 for being appropriately compact.

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 has three parameters, no output schema, and no annotations, the description is too sparse to provide adequate context. It does not mention the note parameter, expected response, or any behavioral details. A mutation tool with this complexity requires a more thorough description to be complete.

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?

The input schema already includes descriptions for all parameters (100% coverage), so the baseline is 3. The description adds no extra semantic meaning beyond the schema, such as format hints or parameter relationships. It relies entirely on the schema for parameter understanding.

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 action ('aktualisiert' = updates) and the resource ('Status einer Bestellung' = order status), making it unambiguous. It distinguishes itself from sibling tools like woo_get_order and woo_list_orders by specifying the update action on the status. The optional note capability isn't mentioned, but the core purpose is specific and clear.

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 no guidance on when to use this tool versus alternatives, such as woo_update_product or other order-related tools. There are no stated prerequisites, exclusions, or context for appropriate usage relative to siblings.

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