generate_motion_snippet

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

No annotations provided, but the description discloses key behaviors: returns specific components (CDN link, code snippet, usage hint, reduced-motion note), includes prefers-reduced-motion guards, and explains that style adjusts easing/duration. This adds value beyond basic purpose.

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 sentences with no fluff. The first sentence states the primary action and return value. Subsequent sentences list categories and note about reduced-motion. Every sentence earns its place.

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 2-parameter tool with 100% schema coverage and no output schema, the description covers what the tool does, what it returns, and key behavioral notes. It does not discuss error handling or usage details, but those are minimal expectations for a generation tool.

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% (both parameters described in schema). Description adds context: 'style adjusts easing and duration', and lists the enum values inline. This enriches the meaning beyond the schema's field descriptions.

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?

Description clearly states it generates an anime.js v4 animation snippet for a given motion category and design style, listing all 8 categories. The verb 'generate' and resource 'motion snippet' are specific, distinguishing it from siblings like generate_template or generate_css_output.

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?

Description provides context on when to use (to get a ready-to-paste snippet) and what is returned (CDN link, code, usage hint, reduced-motion note). It does not explicitly exclude alternatives, but the sibling tools have distinct purposes, making the context sufficiently clear.

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