skylight_get_reward_points

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

No annotations are present, and the description only states what data is returned, not behavioral traits like idempotency, authentication needs, or error handling. For a read operation, it should at least indicate it is read-only.

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 concise sentence that directly states the function and output. No unnecessary words or fluff.

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?

Given the lack of annotations, output schema, and parameter descriptions, the description provides minimal context. It adequately states the core purpose but leaves gaps about the parameter, idempotency, and return format. It is minimally viable but not thorough.

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 only parameter 'frameId' has no description in the schema (0% coverage) and the tool description does not explain its meaning or role. The phrase 'per family member' does not clarify what frameId represents, leaving the agent to guess.

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 'Get', the resource 'reward-point balances', and the scope 'per family member' including both 'lifetime earned + current balance'. It effectively distinguishes from sibling tools like skylight_list_rewards or skylight_get_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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or context. The description lacks information about typical use cases or exclusions.

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