event_stop

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

With no annotations, the description carries the full responsibility for disclosing behavior. It explains the 'immediate' flag's impact on stopping (skipping vs honoring release/fade-out), which is useful, but it does not mention error handling, requirements (e.g., event must be playing), or side effects beyond the stop action.

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 concise, uses a clear structure with an Args list, front-loads the purpose, and contains zero fluff. Every sentence serves a purpose.

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 straightforward stop operation, the description covers the core behavior and parameter details. It lacks information about return values or error states, but given the tool's simplicity and lack of output schema, this is acceptable. It could mention prerequisites (e.g., event must be playing) explicitly, but the phrase 'playing event' implies it.

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 description adds meaningful context to both parameters: target is clarified as an 'event:// path or {guid}', and 'immediate' is explained with its default value and behavioral nuance. Since schema coverage is 0%, this is essential and well done.

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 action ('Stop a playing event instance') with a specific resource, and the mention of 'immediate' behavior differentiates it from other event controls like pause or return-to-start. It is unambiguous and precise.

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 explains the immediate parameter's effect but does not explicitly state when to use this tool versus siblings like event_toggle_pause or event_key_off. The intended use is implied by the verb 'stop', but no exclusions or alternatives are mentioned.

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