Stage Music Time

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

No annotations exist, so the description carries the disclosure burden, and it does a good job: it enumerates the returned fields (playing, url, t in song seconds, duration, loop) and the not-playing case {playing: false}. It omits error/failure conditions and staleness/freshness behavior, keeping it from a 5.

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?

One dense sentence, front-loaded with the resource and immediately followed by the return shape and the intended use. The parenthetical field definitions are compact and earn their place, though the sentence is slightly overloaded.

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?

Output schema exists and the description still explains the payload variants, so return semantics are well covered, and the usage hook is present. The unexplained required 'scene' parameter is the main gap for correct invocation.

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 0% for the single required parameter 'scene', and the description never explains what a scene value is, its format, or whether it identifies a stage scene. The description must compensate at this coverage level and does not.

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?

States a specific resource and verb: reads the song's playback time as the listener hears it, and names the page command (music_time). An agent can distinguish it from stage_music (setting music) and stage_actor_play (using the time) without opening the schema.

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?

Explicitly says to read it in order to place a take on the beat and names stage_actor_play at_music as the consumer. It does not say when not to use it or mention alternatives such as stage_status, but the primary routing is clear.

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