ae_add_button_press

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

Discloses it inserts three Scale keyframes around atTime and assumes 100% scale. No annotations provided; the description adds some context but does not address potential side effects like overwriting existing keyframes.

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?

Two sentences: first defines purpose, second adds technical detail. No wasted words.

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 simple animation tool without output schema, it adequately explains behavior. Missing prerequisites or error handling, but not critical for this type of tool.

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 60%. The description adds context to parameters like atTime and depth, but does not significantly enhance understanding beyond the schema defaults and descriptions.

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?

Clearly states it adds a 'button press' micro-interaction, specifically a scale dip and release. This verb+resource description distinguishes it from sibling tools like ae_add_bounce_expression or ae_add_fade.

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?

Implicitly suggests use before a major movement via 'just before a major on-screen movement begins,' but no explicit when-to-use or alternatives mentioned.

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