android_media_action

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description is not required to restate that this mutates state. The description adds only the minimal context that an active media session is the target. It does not explain side effects of individual actions, such as stop vs pause, or what happens if no session is active, but the annotations cover the safety profile.

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, front-loaded sentence with no wasted words. It is concise, though it could have added valuable behavioral or usage detail without becoming overly long.

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 low-complexity tool with only two parameters, the description plus schema provides a baseline understanding: choose an action and optionally a package name. However, it leaves key operational details unspecified, such as how packageName disambiguates between multiple active sessions and what happens when packageName is omitted.

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%, so the description was expected to compensate, but it mentions neither 'action' nor 'packageName'. The action enum is reasonably self-explanatory, and 'packageName' is recognizable, but the description adds zero semantic detail about how the parameters interact or when packageName is needed.

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 uses a specific verb ('Control') and a resource ('active media session'), clearly indicating that this tool operates on media playback rather than querying it. The distinction from the sibling android_media_sessions is implicit—one lists sessions, the other controls them—though the description does not explicitly name the alternative.

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?

There is no guidance about when to use this tool versus alternatives like android_media_sessions, volume controls, or UI-based interaction. The description implies 'when you want to control media playback' but provides no context on prerequisites such as needing an active session, or when to provide packageName.

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