entities_bulk_set_entity_exposure

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

No annotations are provided, so the description carries full burden. It mentions the underlying WS call, which gives some tech context, but does not disclose authorization needs, idempotency, or whether exposures are additive or replaced.

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?

Three short sentences, each adding value. The purpose is front-loaded, with assistants default in the second sentence and technical detail in the third. No redundant or irrelevant content.

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 bulk exposure tool with an output schema, the description covers the key aspects: bulk operation, assistants default, and underlying mechanism. It lacks details on error handling or return effects, but given schema coverage, it is largely sufficient.

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 description coverage is 0%, so description must compensate. It explains the assistants default and subset usage, but does not elaborate on entity_ids or should_expose beyond their names and types.

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 starts with 'Expose/hide many entities across one or more voice assistants in one call,' which is a specific verb+resource combination. It clearly distinguishes from sibling tools like entities_set_entity_exposure by emphasizing bulk operation.

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 states it's for many entities in one call and explains the default assistants with instructions to pass a subset. It implies when to use the bulk version over the singular one, but does not explicitly mention when not to use it.

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