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

With no annotations, the description carries the full behavioral burden. It usefully discloses that private mascots receive a signed, expiring link and that embeds are live and animated, but it omits permissions, whether calling creates persistent state, expiration details, and any safety or rate-limit context.

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 two tight sentences with no filler, and the core purpose is front-loaded before the private-link caveat. Every sentence contributes useful information.

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 an 8-parameter tool with no annotations and no output schema, the description is too thin. It does not explain the return structure, most parameter behavior, prerequisites, or how the generated embed code should be used.

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%, and the description adds meaning mainly for the framework formats and the private/public link behavior. It does not clarify id, look, props, canvas, trigger, or animation, so several parameters remain under-explained relative to the schema 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 description states a specific verb and resource: getting code to embed a live, animated mascot. It also names supported output formats, which helps distinguish it from broader export tools, but it does not explicitly contrast it with siblings such as export_mascot or export_clip.

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?

The description implies the tool is for obtaining embed code, but it gives no explicit when-to-use guidance, no exclusions, and no alternatives. It does not explain when to choose get_embed_code versus export_mascot or export_clip.

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