labels_assign_label_to_entity

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

With no annotations, the description adds the important detail that existing labels are preserved. However, it does not mention idempotency, permissions, or other side effects. The simple nature of the operation mitigates this slightly.

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?

A single, clear sentence that conveys the essential information without superfluous content. Front-loaded with the critical preservation note.

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 simple two-parameter tool, the description covers the basic purpose. However, the lack of parameter explanations and usage guidance means an agent might need additional context to invoke correctly, especially without annotations or schema descriptions.

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 has 0% description coverage, and the description does not explain what entity_id or label_id refer to or their expected formats. While the tool name provides context, explicit parameter guidance is missing.

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 ('Assign a label to an entity') and a key behavioral detail ('preserves existing labels'). It effectively distinguishes from sibling tools like 'labels_assign_label_to_device' by specifying '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?

The description implies use when assigning a label while keeping existing labels, but provides no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, though sibling tools exist for device assignments and label removal.

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