Get animation template

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read operation' is redundant. The genuinely additive detail is that 'provider scopes, locks and credits apply', which tells the agent about auth context and cost not captured by annotations, though it is boilerplate-level and does not quantify or qualify it.

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?

Three compact clauses with the endpoint front-loaded and zero filler. The fragmentary style and template boilerplate keep it from being exemplary, but nothing is wasted.

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 read tool whose annotations already cover the safety profile, the essentials for invocation are present. Still, with no output schema the description could say what a returned template contains or how missing/unknown uids are handled, and it leaves the account parameter's role unaddressed.

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 coverage is only 50%: the account parameter carries a description but uid does not document its format or semantics. The description adds nothing about either parameter beyond echoing {uid} in the URL, 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 endpoint 'GET /v5/animation_templates/{uid}' states a specific verb and resource, and the {uid} path segment distinguishes it from list_animation_templates by implying a single-item fetch. However it does not name or differentiate from the sibling get_image_template / update_animation_template family in plain language.

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 when-to-use guidance, no mention of when to prefer this over list_animation_templates or how to obtain a uid. 'Read operation' is the only usage-relevant statement and it is a restatement of the annotation, not routing guidance.

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