entities_get_entity

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

The description indicates a read operation ('get'), but no annotations are present. While the behavior is implied to be non-destructive, the description does not explicitly confirm the absence of side effects, permissions required, or any rate limits. This is acceptable but could be improved.

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, focused sentence that efficiently conveys the core purpose. It is front-loaded with the action and resource. However, it may be overly terse given the lack of parameter guidance.

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's simplicity (one parameter, output schema present), the description is minimally adequate. However, it does not elaborate on the return value format or any constraints, which the output schema may cover, but the description adds no contextual completeness beyond the bare purpose.

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 parameter 'entity_id' has no schema description (0% coverage), and the tool description adds no additional meaning beyond its name and type. The description fails to explain what entity_id represents or how to format it, leaving the agent reliant on external knowledge.

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 action ('get'), the resource ('full state and attributes'), and the scope ('single entity'). It effectively distinguishes from sibling tools like entities_list_entities (which returns all entities) and entities_toggle (which changes state).

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 provided on when to use this tool versus alternatives (e.g., entities_list_entities for multiple entities, ws_get_states for streaming). The absence of usage context leaves the agent without decision support.

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