fmod_ParameterProxy_getCursorPosition

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

No annotations provided. Description only states return value, no mention of side effects, permissions, or error behavior. For a getter tool, minimal disclosure.

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?

Description is short but contains a grammatical error ('parameter 's') and includes technical noise '[method ...]'. Could be cleaner without losing meaning.

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?

No output schema. Description states return type (number) but lacks detail on what the cursor position represents or error conditions. Adequate for a simple getter but not comprehensive.

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?

Single parameter 'target' has schema description, but it's generic (path or guid). Tool name implies target should be ParameterProxy, but description doesn't clarify. Schema coverage is 100%, so baseline 3.

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 retrieves cursor position of a preset parameter, and mentions it's within an event context. It differentiates from sibling tools like fmod_Event_getCursorPosition by focusing on preset parameters rather than events directly.

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 on when to use this tool vs alternatives like fmod_GameParameter_getCursorPosition or fmod_ParameterProxy_setCursorPosition. Agent must infer from tool name alone.

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