entities_bulk_control

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

Discloses grouping behavior and return value (dict mapping domain to count). Lacks details on error handling or partial failures, but since no annotations, description provides useful behavioral context.

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?

Two concise sentences with no redundancy. First sentence states action, second explains grouping and return format. Every word 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 an output schema exists, description covers return value and grouping. Could mention error behavior, but overall sufficiently complete for bulk control.

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?

With 0% schema description coverage, description adds critical meaning: entity_ids is a list of entities, action must be one of three values. Explains grouping logic but not entity ID format.

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?

Description clearly states the tool performs bulk turn_on/turn_off/toggle on a list of entities, distinguishing it from single-entity tools like entities_turn_on and entities_toggle.

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?

Explicitly mentions grouping by domain and allowed actions, implying use for bulk operations. Could explicitly state when not to use (e.g., for individual entity control or actions not in list), but sufficiently guides selection.

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