fmod_Event_getPlayheadPosition

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

No annotations are provided, so the description carries full burden. It states the tool retrieves playback position (read operation) but does not disclose what happens if the event is not playing, if the parameter is invalid, or the format of the returned position (e.g., samples, seconds). Minimal behavioral context beyond the function name.

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 short (two sentences plus method reference). The second sentence ('Returns the playback position of a model.') is slightly redundant and could be merged or removed. Overall, it is concise but not perfectly lean.

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 retrieval tool with no output schema, the description should clarify the return format (e.g., position in samples or milliseconds) and potential errors (e.g., if parameter doesn't exist). It lacks these details, making it incomplete for an agent to fully understand the tool's behavior.

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 description coverage is 100%, providing clear definitions for both 'target' and 'parameter'. The description adds no additional meaning beyond 'a given parameter', which is redundant. Baseline 3 is appropriate as schema does the heavy lifting.

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 it retrieves the playback position of a given parameter from an event, which is specific. The method reference adds clarity. However, it could be clearer that 'parameter' refers to Timeline or GameParameter within the Event context, and it doesn't explicitly distinguish from siblings like fmod_Parameter_getPlayheadPosition.

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?

There is no guidance on when to use this tool versus alternatives such as fmod_Event_getCursorPosition or fmod_Parameter_getPlayheadPosition. The description does not mention prerequisites, typical use cases, or exclusions.

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