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

Annotations already declare it as read-only, idempotent, closed-world, and non-destructive. The description adds substantial context beyond that: it lists the template details returned, notes that credit balance appears when signed in, and instructs the agent to tell the user the price in credits. It does not contradict any annotation.

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 front-loaded with what the tool shows and then gives usage guidance. It is somewhat list-heavy in enumerating return values despite having an output schema, but the details are relevant and there is little wasted wording.

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?

Given rich annotations, a complete input schema, and an output schema, the description supplies the remaining context an agent needs: when to call it, its relationship to run_template, and the user-facing instruction to disclose price in credits. Nothing critical appears missing.

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?

There is one required parameter with 100% schema description coverage. The schema already explains that slug comes from search_templates, and the description does not add syntax or format details beyond that baseline.

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: show one MakeViral template. It distinguishes this from sibling tools by saying to use it when the user names or picks one template and to call it before run_template, so an agent can tell it apart from search/list/run operations.

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?

It gives clear usage context: use when the user names or picks one template, and call it before run_template to pass the right version and photos. It does not explicitly say when not to use it or name search_templates as the alternative for finding an unknown template, though the schema references search_templates for the slug.

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