skylight_list_rewards

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

The readOnlyHint annotation already indicates this is a read operation, so the bar is lower. The description adds a useful behavioral default ('last 30 days') and frame scoping, but it does not mention output shape, date format, pagination, or whether frameId is required.

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, tightly written sentence. It front-loads the action and resource while packing in the key default behavior with no filler.

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 straightforward read-only list tool, the description communicates the core purpose and default filtering, but it leaves out useful operational details such as return format, date value formatting, and whether frameId is required. Since there is no output schema, the description could have provided more completeness.

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%, so the description must compensate, but it only partially does. It implies frameId is tied to the Skylight frame and that redeemed_at_min/max relate to the time window, but it does not explain their formats, optionality, or exact meaning.

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 ('redeemed rewards for a Skylight frame'), and adds a clear scope with 'defaulting to the last 30 days.' This distinguishes it well from sibling tools like skylight_get_reward, which retrieves a single reward, and reward mutation tools.

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?

The description gives useful context by stating the tool lists redeemed rewards for a specific frame with a default time window. However, it does not explicitly state when to use this tool over alternatives, nor does it mention exclusions or provide comparison to skylight_get_reward or reward-management siblings.

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