ha_list_services

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

No annotations provided; description only states it's a list operation. Fails to disclose any potential side effects, rate limits, or access requirements. For a read-only tool, minimal but insufficient for full transparency.

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?

Single sentence with verb first, no filler. Effectively communicates purpose and parameter in a compact form.

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?

Covers purpose and parameter, but lacks description of return format or behavior when no domain filter is applied. Without an output schema, agent may not know what to expect.

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 already documents the 'domain' parameter with its description. Description merely restates that it's optional, adding no additional semantic value 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?

Description clearly states verb 'list', resource 'available services', and optional filter by domain. Distinguishes from sibling list tools by specific resource 'services'.

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?

Implied usage for listing services, but no explicit guidance on when to use this vs alternatives like ha_get_entity or ha_call_service. No exclusion criteria or contextual hints provided.

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