ha_search

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two things beyond the annotations: authentication context ('using the Home Assistant plugin's saved login') and the un-filtered fallback behavior of returning areas and domains rather than entities. It does not discuss pagination or result ordering, but that is minor here.

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?

Two short sentences, front-loaded with the core verb+resource and no redundant restatement of the name or title. Every clause carries information (returned fields, auth source, fallback behavior).

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?

An output schema exists, so return-value explanation is unnecessary and correctly absent. What remains is covered: what is searched, the four filter parameters implied, and the no-filter behavior. Only the otherwise-undocumented limit parameter is left unaddressed.

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 coverage is 75% (limit has no description), so the schema does most of the work for area, query and domain. The description's mention of 'filters' and the no-filter case hints that the null defaults are pass-through filters, but it adds no syntax, format, or matching-rule detail beyond the 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 even enumerates the fields returned (id, name, state, area), so the agent knows this is a discovery/search operation. It does not name the closely related siblings (ha_describe_entity, ha_call_service), so the distinction is inferable but not stated.

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 phrase 'to put on keys' implies a use context, and 'With no filters, lists the areas and domains' tells the agent how to use it for browsing. However, there is no explicit guidance on when to prefer ha_describe_entity or ha_call_service, nor any stated exclusions.

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