skylight_delete_reward

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

The annotations already indicate destructiveHint=true and readOnlyHint=false, so the destructive nature is known. The description adds no extra behavioral context, such as irreversibility, side effects, required permissions, or consequences for redeemed rewards. It merely repeats the word 'delete.'

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 text is short and front-loaded, but it is under-specified rather than efficiently complete. The single sentence adds essentially no information beyond the tool's name and therefore does not earn its place as a useful description.

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 destructive operation with two undocumented parameters and no output schema, 'Delete a reward' is inadequate. The agent has no explanation of what a reward is, which ID to provide, or how frameId relates to the deletion. The description provides only the barest hint of the tool's purpose.

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%, and the description does not mention 'id' or 'frameId' at all. The schema only provides types and requiredness, leaving the meaning of these parameters entirely unexplained. The description fails to compensate for the lack of parameter documentation.

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 and resource: 'Delete a reward.' It is clear about the operation and target. However, it does not differentiate this from sibling tools like skylight_unredeem_reward or skylight_delete_meal; it is essentially a direct restatement of the function name.

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?

There is no guidance on when to use this tool versus alternatives. No conditions, prerequisites, or exclusions are stated. The agent is left to infer from the name alone when to pick delete_reward over related reward or delete tools.

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