List animations

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered without the description. The description does add real context beyond them by noting that provider scopes, locks and credits apply - useful for knowing the call consumes credits and requires auth - but it remains vague about what those constraints concretely mean.

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 short, front-loaded sentences with no filler. Nothing is wasted, though the leading REST path is arguably more implementation detail than useful signal.

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?

No output schema exists, and the description says nothing about what an animation entry contains, result ordering, or pagination behavior for a tool whose whole purpose is retrieving a list. With a 2-param schema and no return documentation, an agent lacks enough to call this confidently.

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?

Only 50% of the schema has descriptions (account is documented, page is not, including no explanation of what 'page' paginates). The description adds nothing about either parameter, so it fails to compensate for the coverage gap.

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 title and endpoint 'GET /v5/animations' imply fetching a collection of animations, but the description never states this in words - it only exposes a REST path. It also does nothing to distinguish this listing operation from siblings like get_animation, create_animation, or animate_template.

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 call this versus get_animation or animate_template, nor any note on pagination expectations for a list endpoint. The only usage signal is the bare label 'Read operation'.

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