skylight_set_default_calendar

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

No annotations are present, so the description carries the full behavioral burden. It indicates a state change ('Set'), but does not disclose whether this affects only future events, whether existing defaults are overwritten, what permissions are required, or whether the change is scoped to a household, frame, or user.

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 clear sentence with no filler or redundancy. It front-loads the core action and target resource efficiently.

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 annotations, a missing description for 'frameId', and no output schema, the description is too sparse. It establishes the basic purpose but leaves important context about parameter meaning, side effects, and result behavior unaddressed.

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 schema documents only 'id' (50% coverage) and leaves 'frameId' completely undescribed. The description does not compensate by explaining how the parameters relate or what 'frameId' means, so an agent cannot confidently populate both parameters.

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 ('Set'), a specific resource ('default source calendar'), and the scope ('for new events'). This clearly distinguishes it from sibling operations like creating, listing, or categorizing source calendars.

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 use this tool versus alternatives such as skylight_update_calendar or skylight_create_source_calendar. The description implies a configuration purpose but does not state when the default should be changed or what alternatives exist.

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