fmod_Event_returnToStart

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

No annotations are provided, so the description fully covers behavioral aspects: it moves to cursor or start based on state. It discloses the condition-dependent behavior but does not mention side effects like whether playback restarts, or error handling. Still, for a simple action, it is transparent enough.

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 one well-structured sentence that front-loads the action. It is not overly verbose, though the method reference could be considered extraneous. No wasted words.

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 the tool is simple with one parameter and no output schema, the description covers the core functionality. It does not specify return values or error cases, but for a playback control action this is acceptable. Mostly complete.

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% with a clear parameter description. The description adds no additional meaning beyond what the schema already provides, so baseline 3 applies.

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 moves the playback position, specifying different targets based on event state (playing/stopping/paused vs. stopped). It uses a specific verb and resource, and distinguishes from sibling tools like fmod_Event_getCursorPosition or fmod_Event_setCursorPosition.

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 usage when resetting playback position, with conditional behavior explained. However, it does not explicitly state when not to use it or compare with alternatives like fmod_Event_play or fmod_Event_keyOff. The context is clear but lacks explicit guidance.

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