Search entities

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: the returned fields (entity_id, name, state, area) and the result ordering ('best matches first'). It does not mention limit/pagination behavior or what happens when nothing matches, which is why it stops short of 5.

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?

Three short lines, front-loaded with purpose, followed by the workflow hint and the return shape. No filler sentences and nothing repeated from the schema.

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?

Annotations cover read-safety, an output schema covers return structure, and the schema fully documents all four parameters. The description supplies exactly the missing piece — the discovery-then-detail workflow with get_entity_state — so an agent has everything needed to call it 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?

Schema description coverage is 100%, and the schema already documents query matching semantics, area, domain, and limit with a max of 100. The description adds no parameter-level detail (no note that an empty query lists everything, no guidance on combining filters), so this is the baseline for a fully documented schema.

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 ('Find Home Assistant entities and their current states') and immediately distinguishes itself from the sibling read tool by naming get_entity_state for details. An agent can tell what this does and how it differs from adjacent tools without opening a schema.

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?

Explicitly says 'Use this first to discover entity_ids, then call get_entity_state for details', which gives both the ordering rule and the named alternative. The condition that selects this tool versus get_entity_state is unambiguous.

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