entities_list_entities

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

No annotations provided, so description bears full responsibility. Only states 'list' which is read-only, but lacks details on behavior such as pagination, sorting, valid domain values, or whether it returns all entities or only active ones. Minimal disclosure.

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 of 13 words, front-loaded with 'List all entities'. No unnecessary words or repetition. Efficiently conveys purpose and filtering capability.

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?

For a simple listing tool with output schema, the description is fairly complete. It misses details on domain parameter validation and return set scope, but overall adequate. Slight improvement possible.

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 has 0% coverage, but description explains the domain parameter with examples (light, switch, sensor...), adding meaning beyond the schema definition. Could specify case sensitivity or exact matching, but still helpful.

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 'List all entities' with optional domain filter. Verb and resource are specific, and it distinguishes from sibling listing tools by indicating it lists all entities, not just registry or exposed ones.

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?

Description implies usage for broad entity listing. No explicit when-to-use or when-not-to-use, nor mention of alternatives like entities_list_entity_registry or entities_list_exposed_entities. Guidance is lacking.

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