skylight_update_calendar

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

Without annotations, the description is the sole source of behavioral info. 'Set which... are active' implies mutation and replacement of the active set, but does not explicitly state what happens to unspecified calendars, whether it is additive, or what the response is. The optional frameId parameter is unexplained. Key behavioral details are missing.

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 short sentence, but its brevity sacrifices clarity. It conveys the core purpose but lacks necessary details, making it under-specified rather than efficiently concise.

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 no output schema and no annotations, the description should cover return values, prerequisites, and behavioral context. It only states the high-level operation, missing critical information for a mutation tool with multiple parameters and complex side effects (deactivating calendars).

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?

With only 33% schema description coverage, the description should add meaning. It only restates the active_calendars parameter as 'Calendar ids to keep active', which adds minimal value. The id and frameId parameters are not described at all, leaving their purpose unclear.

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 clearly states the verb 'Set' and the resource 'sub-calendars of a connected account', specifying the action of making certain calendars active. This distinguishes it from sibling tools like skylight_set_default_calendar or skylight_link_apple_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?

No guidance on when to use this tool versus alternatives like skylight_create_source_calendar or skylight_delete_source_calendar. No prerequisites or context (e.g., needing a connected account) are mentioned.

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