list_entities

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

No annotations are provided, so the description carries full behavioral burden, yet it only says 'List'. It does not confirm read-only behavior, describe the return shape (entity IDs and friendly names?), note result size/pagination, or mention whether filters are ANDed together. For a list tool with zero annotation coverage this is thin.

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?

One summary line followed by a compact per-argument list; nothing is padded. The purpose is front-loaded before the arg details, though the extra blank lines and Args formatting are slightly noisy.

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?

With no output schema and no annotations, the description should say more about what comes back (fields per entity) and how filters combine. The argument coverage is good, but the return side and interaction of filters remain unspecified.

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 the description must compensate, and it largely does: each of the three parameters is explained with a concrete example domain ('light'), area ('Woonkamer'), and match semantics ('substring match against entity_id or friendly name'). The case-insensitivity note for area is a useful detail the schema lacks.

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?

States a specific verb and resource ('List Home Assistant entities') plus the filter scope, so the purpose is immediately clear. However, it does not distinguish itself from close siblings like list_registry_entities, which an agent could easily confuse with it.

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 on when to use this versus list_registry_entities or get_state. The presence of filters implies a browsing use case, but the agent is left to infer that and has no stated exclusions or prerequisites.

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