skylight_get_event_notification_settings

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds that the settings are scoped to a frame, but it does not disclose error behavior, auth requirements, or what happens when no settings exist. No contradiction with annotations is present.

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, direct sentence with no filler or redundant content. Its subject-verb-object structure is front-loaded and every word contributes 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 getter, the description covers the basic purpose but leaves important gaps: frameId requiredness is ambiguous, the return value is not described, and there is no output schema to compensate. An agent could not confidently invoke this tool correctly based solely on the description.

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 has 0% description coverage and the description does not explain frameId, its format, or whether it is required. The phrase 'the frame's' weakly implies a frame identifier is needed, but the schema declares no required parameters, leaving an agent uncertain about whether frameId must be supplied.

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 ('Get') and a concrete resource ('the frame's calendar-event notification settings'), which clearly identifies the operation. It also distinguishes the tool from its sibling skylight_update_event_notification_settings by making the read-only nature explicit.

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 usage guidance is provided. The description does not say when to use this getter versus the update sibling, nor does it mention any prerequisites or context such as needing the frameId from skylight_list_frames.

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