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

Annotations already cover the read-only/idempotent/non-destructive safety profile, so the bar is lower, but the description still adds substance: no account needed, SRI-pinned versions, per-framework output, and special handling for motion clips. It does not describe response shape/pagination, but as a read tool with no output schema it discloses the important behavioral traits.

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?

Dense and front-loaded with the core promise ('free, no account needed... returns working code'), then enumerates variants and defaults. Slightly long but every sentence, including the age/license routing note, carries operational value.

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?

There is no output schema, so the description assumes the burden of describing returns, and it does: the four code variants, the default-selection behavior, the `all` mode, and motion-clip output. An agent has everything needed to call this correctly.

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 100%, so baseline is 3, but the description adds genuine semantics: omitting `framework` yields the best-fit variant, and `all` returns every applicable variant. It also explains that motion clips route to three.js code, which the schema does not convey.

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?

States a specific verb+resource: returns working, paste-ready code that renders one catalog item across four named output forms. It also distinguishes itself from the sibling get_catalog_item by naming that tool for metadata/license needs.

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?

Explicitly says when to use it ('when you are ready to put a catalog item on a page or in an app') and names the alternative for a different need ('call get_catalog_item first if you still need its license or metadata'). Both the trigger and the exclusion are stated.

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