entities_get_entity_exposure

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

No annotations are provided, so the description must disclose behavioral traits. It implies a read-only operation ('Get') but does not specify whether the tool has side effects, requires special permissions, or what the response format includes. The description adds minimal value beyond the action itself.

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 a single sentence, concise and front-loaded. However, given the lack of detail elsewhere, it could be slightly expanded without harming conciseness.

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 tool with one parameter and an output schema, the description adequately states the core purpose but omits details about return values or behavior. The presence of siblings and the absence of annotations lower completeness, but the tool is simple enough that the description is minimally viable.

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 one parameter 'entity_id' with no description (0% schema coverage). The description does not clarify expected format or domain for entity_id, such as whether it should be an entity registry ID or a friendly name. The parameter name is self-explanatory, but the description fails to compensate for the schema gap.

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 uses a specific verb 'Get' and clearly identifies the resource 'exposure flags' for a single entity, distinguishing it from siblings like 'entities_set_entity_exposure' and 'entities_list_exposed_entities'. It also specifies the scope 'across all voice assistants', which adds useful context.

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?

No guidance is given on when to use this tool versus alternatives such as 'entities_list_exposed_entities' (for all entities) or 'entities_set_entity_exposure' (for modifying exposure). The description does not mention prerequisites or 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.