list_registry_entities

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

With no annotations provided, the description carries the full behavioral burden. It usefully enumerates the returned fields and states the tool is for finding duplicates/orphans, but it does not disclose whether the operation is read-only, what permissions are needed, pagination behavior, or any side effects.

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 front-loaded with the tool's purpose, followed by the returned fields and a use case. It is efficient and contains no obvious filler, though the field listing is dense and could be slightly tighter.

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 no output schema, no annotations, and six undocumented filter parameters, the description is incomplete. It covers return fields adequately but leaves all input parameter behavior unexplained, which is a significant gap for an agent trying to invoke the tool correctly.

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?

There are 6 input parameters with 0% schema description coverage, so the description must compensate. It only vaguely gestures at filtering with 'filter by integration' and never explains domain, area_id, disabled, platform, device_id, or config_entry_id, leaving most parameter semantics undocumented.

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 states a specific verb and resource: 'List entries from HA's entity_registry with full details.' It is clear what the tool does, but it does not distinguish itself from the sibling 'list_entities' or explain why an agent would choose this over that tool.

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 gives an explicit use case: 'Use this to find duplicates, orphans, or filter by integration.' However, it names no alternatives and gives no conditions for when not to use it, so the usage guidance remains implied rather than complete.

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