manage_tween

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

Since no annotations are provided, the description carries the full disclosure burden. It reveals that create does not play, that playback occurs live in the viewport, and that pause/resume/cancel can target individual or all tracked tweens. Missing details include error handling and state persistence, but the core behavioral traits are covered.

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 dense but efficient, packing action semantics and parameter aliases into a single well-structured sentence. Every phrase adds value; no filler.

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 11-parameter tool with no output schema and no annotations, the description gives a solid conceptual overview but omits detailed parameter semantics and return behavior (e.g., what play/pause return). The nested tweenInfo object is only hinted at via the example, making it less complete than ideal.

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?

The schema has only 36% description coverage, and the description adds meaning for key fields (goal/properties alias, tweenId, action semantics). However, duration, tweenInfo, easing fields, and repeatCount remain undocumented, leaving a substantial gap for a low-coverage schema.

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 clearly states the tool's function—animating properties via TweenService—and differentiates it from sibling tools like manage_animation by specifying the live-viewport playback and action set. The verb 'Animate' plus resource 'TweenService' makes the purpose unambiguous.

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 provides explicit guidance on actions (create, play, pause, resume, cancel/stop_all) and explains when to use tweenId vs path+goal. It does not explicitly call out alternatives, but the context is clear enough for an agent to choose it for tweening tasks.

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