skylight_delete_reward

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

With no annotations, the description should disclose operation traits like irreversibility, permission requirements, or side effects. It only states 'Delete a reward', adding no behavioral context beyond what the name implies.

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 extremely concise (three words) but fails to convey necessary details. It is under-specified rather than efficiently structured, lacking definition of parameters or usage context.

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 tool's complexity (delete operation, two parameters, no output schema, no annotations), the description is severely incomplete. It omits critical information about parameter semantics, return values, and operational behavior, rendering it inadequate for correct selection and invocation.

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 input schema has two parameters (id, frameId) with no descriptions, and schema coverage is 0%. The description does not explain what these parameters mean, how they relate, or which is required. The agent cannot determine how to correctly populate them.

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 'Delete a reward' clearly states the action and resource, matching the name. However, it does not differentiate from sibling delete tools like skylight_delete_chore or skylight_delete_event, which perform analogous operations on different entities.

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. There is no mention of prerequisites, context, or conditions for use, leaving the agent to infer purely from the name.

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