skylight_list_calendars

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds a useful behavioral detail by specifying 'active calendars' as the filtered result, but it does not disclose pagination, authentication requirements, or response shape. That is acceptable for a simple read-only list, but not deeply transparent.

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, front-loaded, information-dense sentence with no filler or redundant phrasing. Every word contributes to the meaning.

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 one-parameter read-only list, the description conveys the core result type — accounts and active calendars — but it leaves the critical frameId parameter semantically under-specified and gives no guidance about related calendar tools. The tool is simple, but the absence of parameter clarity is a notable completeness gap.

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 0%, and frameId has no schema-level documentation. The description implies that frameId identifies the frame whose calendars are listed, but it does not clarify whether it is effectively required, its format, or what happens if it is omitted. Given the low coverage, the description only partially compensates.

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 names a specific verb ('List'), a concrete resource ('the frame's calendar accounts (Google/Apple/etc.) and their active calendars'), and a scope ('frame'). It is clear about what the tool returns, though it does not explicitly contrast itself with sibling tools like skylight_list_source_calendars or skylight_get_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?

There is no guidance about when to prefer this tool over alternative calendar-related tools, nor any mention of exclusions or prerequisites. The only implied usage is 'when you need the frame's calendar accounts and active calendars,' but no alternatives are called out.

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