Remove label from entity

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, but the description goes further: it explains the read-modify-write mechanism, that only the named label is dropped while others are preserved, the exact return keys (entity_id, labels, raw result, ok), and the error payload shape. This is unusually rich disclosure.

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?

Front-loaded one-line summary followed by labeled Use when / Not for / Returns / Errors sections. Every sentence carries distinct operational information; nothing is padding.

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?

For a two-parameter mutation with no nested objects, the definition covers purpose, routing, mechanism, return values, and error behavior. Even though an output schema exists, the explicit error shape disclosure closes the remaining gap an agent would face.

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 coverage is 100% and both parameters are documented in the schema with examples and a pointer to labels_list_labels. The description restates label_id but adds no syntax or format detail beyond structured fields, so baseline 3 applies.

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?

Specific verb+resource ('Remove a label from an entity') plus the exact mechanism (read labels list, drop label_id, write back via WS config/entity_registry/update). It is clearly distinguishable from labels_delete_label and labels_assign_label_to_entity.

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?

Explicit 'Use when: untagging one entity from a label without touching its other labels' and 'Not for: deleting the label itself everywhere — use labels_delete_label'. Both the positive trigger and the alternative are named, leaving nothing to inference.

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