entities_set_entity_exposure

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

The description mentions the underlying WebSocket event ('homeassistant/expose_entity'), which adds transparency about the mechanism. However, with no annotations provided, it does not disclose potential side effects, permissions, or whether the change is immediate.

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 brief with two sentences covering purpose, allowed assistant values, and underlying WebSocket. It is efficient but could benefit from a more structured format (e.g., listing parameters).

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 an output schema (though not shown), the description need not explain return values. However, it lacks completeness in terms of behavioral context (e.g., what happens if the entity is already exposed, or error cases).

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 0%, so the description must compensate. It lists allowed values for 'assistant' but does not explain each parameter in detail. Parameter names are self-explanatory, but the description adds minimal additional meaning beyond the schema.

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 verb (expose/hide), the resource (entity), and the target (voice assistant). It distinguishes from similar tools like entities_get_entity_exposure and entities_list_exposed_entities.

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?

While the purpose is clear, the description does not explicitly state when to use this tool versus alternatives (e.g., get/list exposure). It lists allowed assistant values, but no guidance on prerequisites or when not to use.

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