skylight_list_events

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

Beyond the readOnlyHint annotation, the description adds a valuable security note about third-party calendar data being treated as data, not instructions. This addresses potential prompt-injection risks and gives context about data provenance, which is beyond the annotation.

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?

Two sentences with no fluff. The primary purpose is front-loaded, and the security note is appended without redundancy. Every word earns its place.

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 list operation, the description covers the essential usage and adds a security warning. However, it does not mention output format or pagination, and the optional frameId behavior is left to schema inference. Given the simplicity and annotations, it is adequate but not exhaustive.

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 75%, with date_min, date_max, and timezone already described. The description mentions 'date range' which maps to the required parameters but does not add further detail on frameId optionality or timezone defaults beyond the schema. It stays at the baseline for high coverage.

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 (list), resource (calendar events), and scope (date range for a Skylight frame). It distinguishes from siblings like skylight_get_event (single event) and skylight_create_event (create), making the tool's purpose unambiguous.

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?

It provides clear context by specifying the date range and frame, but does not explicitly mention alternatives or exclusions. However, the purpose itself implies when to use it (listing multiple events) versus other event operations, so it meets the 'clear context, no exclusions' criterion.

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