fmod_Event_stopNonImmediate

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

No annotations are provided, so the description carries the sole burden of behavioral disclosure. It mentions 'enter the stopping event state' but does not explain what that means, side effects, or safety (e.g., destructive vs. read-only). This is insufficient for a state-changing command.

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, concise sentence with no wasted words. It includes a reference to the method. However, it could be slightly clearer by removing the extra spaces around the period.

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 a command that changes state, the description is minimal. It does not explain what happens after stopping, return values (though no output schema), or error conditions. The parameter schema is well-described, but overall completeness is lacking for a non-trivial operation.

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 input schema has 100% coverage with a clear description for the target parameter. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 it commands a playing event instance to enter the stopping event state, using a specific verb and resource. It distinguishes from siblings like fmod_Event_stopImmediate and fmod_Event_play by indicating the action is for a playing instance and the method name is included.

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 versus alternatives like stopImmediate or play. It does not specify prerequisites (e.g., event must be playing) or exclusions. The description lacks explicit usage context.

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