skylight_list_source_calendars

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

The readOnlyHint annotation already covers the safe read-only nature, and the description adds no behavior beyond restating the listing operation. There is no mention of what 'linked' implies, pagination, auth requirements, or other behavioral traits.

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 sentence with no wasted words. It efficiently conveys the action, resource, and scope.

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 one-parameter read-only list tool, the description is adequate at a basic level: it states what is listed and for what scope. However, it lacks usage guidance, parameter clarification, and any mention of what the response contains, so there are clear gaps for an agent invoking it independently.

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 the only parameter, frameId, has no schema description. The phrase 'for a frame' minimally implies that frameId identifies the frame, but it does not clarify whether it is required, its format, or how the frame is specified.

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 uses a specific verb ('List') and resource ('linked source calendars (Google, etc.)') and scopes it to a frame. The phrase 'source calendars' and 'linked' distinguishes this from the sibling skylight_list_calendars without requiring schema inspection.

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 on when to use this tool versus alternatives like skylight_list_calendars or skylight_get_calendar. It does not state prerequisites, exclusions, or conditions that would help an agent choose between related tools.

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