clear_keyframes

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

Annotations already indicate destructive behavior, and the description reinforces this by saying 'Hapus semua' (delete all). It adds useful context beyond the annotation by explaining that setting property to 'all' removes all keyframes, which is not evident from the schema or annotations alone.

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, compact sentence with no filler. It front-loads the main action and includes a parenthetical clarification. However, it sacrifices some clarity for brevity, so not a perfect score.

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 tool, the description provides minimal context. It does not mention return values, reversibility, or whether the action must be the active one. The output schema is present but not shown, so the description cannot rely on it to explain outcomes.

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?

With 0% schema description coverage, the description must compensate, but it only clarifies the special 'all' value for the property parameter. It does not explain the object_name parameter, other possible property values, or the default 'location', leaving significant ambiguity for agent use.

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 action ('Hapus' meaning remove) and the resource ('keyframe properti' from the object's action). It distinguishes itself from animation creation tools like insert_keyframe and animate_location, though it could be more explicit about targeting keyframes specifically.

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. It does not mention prerequisites, target selection, or complementary tools, leaving the agent to infer usage from the name and description.

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