fmod_Parameter_getPlayheadPosition

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

The description claims 'retrieves', implying a read-only operation, but the schema includes an optional 'value' parameter for assigning a new value, indicating the tool can also write. This contradiction is not addressed in the description. Additionally, no information about return values or side effects is provided.

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 a single sentence that is concise and front-loaded with the key purpose. The appended reference '[property · Parameter.getPlayheadPosition]' adds minor overhead but does not detract significantly.

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 has two parameters and no output schema, the description should explain the return value format (e.g., time units) and clarify the write capability. It fails to do so, leaving significant gaps in understanding.

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%, so the schema already documents both parameters clearly. The description adds no additional meaning beyond what the schema provides, meeting the baseline for this dimension.

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 'retrieves the playback position of a parameter', specifying the verb and resource. It mentions the context (associated model.Event), but does not explicitly differentiate from the sibling tool 'fmod_Event_getPlayheadPosition', which likely operates at the event level.

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?

No guidance is provided on when to use this tool versus alternatives like 'fmod_Event_getPlayheadPosition'. The description lacks any contextual direction for usage.

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