get_element_animations

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

Annotations are absent, and the description only states 'Get detailed animation information' without disclosing side effects, return format, or whether it requires an open page or existing element. This leaves the agent unsure about the tool's behavior beyond the basic action.

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, direct sentence with no unnecessary words, and the key action is front-loaded.

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?

The description is minimal and leaves important context unexplained: what 'detailed animation information' includes, whether a page must be loaded, and how it differs from related tools like get_animation_css. Despite the simple schema, the lack of output schema and annotations makes this incomplete for an agent to select reliably.

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 fully documents the 'selector' parameter ('CSS selector for the element'), and the description adds no additional semantics. Baseline of 3 applies given 100% schema coverage.

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 ('Get') and object ('detailed animation information') with a scoping selector. It distinguishes from siblings like get_animation_css (which likely returns CSS) by focusing on animation info for a specific element, but doesn't explicitly differentiate from all related tools.

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 provided. The description does not specify when to use this tool versus alternatives such as watch_element or trace_animation_execution, nor does it mention prerequisites or exclusions.

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