entities_get_entity_exposure

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

No annotations are provided, so the description carries the full burden. It only states 'Get', implying a read operation, but does not disclose any behavioral traits such as required permissions, idempotency, or side effects. The presence of an output schema partially compensates.

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 with 10 words, concise and front-loaded. Every word earns its place, and there is no redundant or irrelevant information.

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 one simple parameter and an output schema, the description is nearly complete. It covers the essential purpose, and the output schema likely details the exposure flags. However, it lacks any behavioral context, which could be added without bloat.

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 single parameter 'entity_id' is not described in the schema (0% coverage). The description does not add any meaning beyond the schema, failing to compensate for the lack of documentation. Even though the parameter type is simple, the description should at least indicate the expected format or source.

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 'Get', the resource 'exposure flags for an entity', and the scope 'across all voice assistants'. It distinguishes from siblings like 'entities_set_entity_exposure' and 'entities_list_exposed_entities' by specifying retrieval.

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 does not provide any guidance on when to use this tool versus alternatives such as 'entities_set_entity_exposure' or 'entities_list_exposed_entities'. An agent would have to infer usage from the verb alone, which is insufficient for optimal tool selection.

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