ha_get_calendars

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool lists entities (read-only), but does not mention permissions, rate limits, or context about what is returned. The lack of output schema means return format is unknown.

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 a single sentence of 6 words, perfectly concise with no fluff. It front-loads the purpose and is appropriately short for a parameterless list tool.

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 zero-parameter tool with no output schema, the description provides the essential purpose but lacks details on return type or potential errors. It is minimally viable but could be improved to specify that it returns a list of calendar entities.

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?

The input schema has no parameters, so schema coverage is 100%. The description adds no parameter information, which is acceptable since there are none to describe. Baseline for 0 parameters is 4.

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 'List all calendar entities in Home Assistant' uses a specific verb 'List' and clearly identifies the resource 'calendar entities' and scope 'all'. It distinguishes itself from sibling tool 'ha_get_calendar_events' which focuses on events of a specific calendar.

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 implies that to list calendar entities, use this tool, and to get events, use ha_get_calendar_events. However, no explicit guidance on when to use vs alternatives or prerequisites is provided.

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