ha_get_calendar_events

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It only states the core function without detailing return format, default date ranges, pagination, or potential errors. The defaults (start=now, end=+7 days) are in the schema but not highlighted in the description.

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, concise sentence with no unnecessary words. It efficiently conveys the core purpose. However, a bit more detail (e.g., date range) could enhance utility without bloating.

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?

Given the lack of output schema, the description should provide some context on return values. It does not mention that events are returned as a list or any properties (e.g., summary, start, end). The tool is simple, but the minimal description leaves agents uninformed about the structure of results.

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%, with clear parameter descriptions including examples and defaults. The tool description adds no additional meaning beyond the schema, which already adequately defines the parameters. Baseline score of 3 is appropriate as the schema handles semantics.

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 'Get events from a specific calendar entity' clearly states the action (get events) and resource (specific calendar entity). The name and entity_id parameter hint at specificity, distinguishing it from sibling ha_get_events which likely returns all events. However, it does not explicitly differentiate or mention date range, leaving some ambiguity.

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?

No guidance on when to use this tool versus alternatives like ha_get_events or ha_get_calendars. No prerequisites or when-not-to conditions are provided, leaving the agent to infer usage independently.

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