skylight_list_rewards

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

No annotations provided; description only mentions listing and default time range. Fails to disclose read-only nature, authentication needs, rate limits, pagination, or empty result behavior.

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?

Single sentence, 12 words, front-loaded with key action. Efficient but omits parameter detail; could expand slightly without losing conciseness.

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?

Adequate for a simple list tool: states resource, context, default filter. However, no result description (output schema absent), no parameter details, and no mention of required permissions. Leaves gaps for an agent.

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 coverage 0% and description adds no parameter explanations. 'defaulting to last 30 days' hints at date parameters but doesn't specify format or that redeemed_at_min/max set range. Parameter names are self-explanatory but lack validation guidance.

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?

Description clearly states verb 'List', resource 'redeemed rewards', and scope 'for a Skylight frame' with default time range. Distinguishes from siblings like skylight_get_reward (single) and skylight_create_reward.

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?

Implies usage for recent redeemed rewards via default 30 days, but no explicit when-not or alternatives. Missing prerequisites like requiring frameId, and no contrast with skylight_get_reward or skylight_redeem_reward.

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