fmod_Event_isPlaying

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

The description uses 'reports' and 'returns true if playing', implying no side effects, but does not explicitly state that the tool is non-destructive or provide additional behavioral context like performance implications or return format details.

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 very short, with only two sentences. However, there is slight redundancy between the first and second sentence; a single sentence would suffice 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?

The description is adequate for a simple query tool with one parameter, but it could be more complete by explicitly stating the return type (true/false) and noting that the tool does not modify state, especially given the absence of an output schema.

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 covers 100% of parameters with good descriptions. The tool description adds no new information about the 'target' parameter beyond what the schema provides, achieving the baseline for complete schema coverage.

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 verb 'reports' and the resource 'whether an event instance is playing', directly indicating the tool's function. It distinguishes from sibling tools like fmod_Event_play or fmod_Event_stop by focusing on status checking.

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 provides no guidance on when to use this tool versus alternatives, such as fmod_Event_isPaused or fmod_Event_isStopping. It does not specify that this is a read-only query or when it's appropriate.

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