skylight_list_rewards

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the useful behavioral detail that results default to the last 30 days, but says nothing about pagination, result ordering, or what happens when date bounds are supplied.

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?

A single front-loaded sentence with no filler; the scope and default behavior come first and nothing is wasted.

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?

No output schema and a read-only list tool, so return format need not be described, but for a 3-parameter tool with 0% schema coverage the description leaves date syntax, optionality of frameId, and pagination 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?

Schema description coverage is 0%, so the description must compensate. It does explain the default date window, which gives meaning to redeemed_at_min/redeemed_at_max, and 'for a Skylight frame' ties to frameId, but it omits date formats and whether the optional bounds override or narrow the default.

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?

Specific verb 'List' plus resource 'redeemed rewards' scoped to a Skylight frame, which distinguishes it from get_reward, create_reward, and redeem_reward. It does not explicitly name a sibling it must not be confused with, but the purpose is 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?

The default 30-day window implies when the tool is useful (recent redemption history), but there is no explicit when-to-use/when-not, nor a pointer to alternatives such as get_reward for a single reward or get_reward_points for point balances.

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