firefox_media

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the description should clarify which actions mutate page state; it instead lumps inspect together with play/pause/seek without saying inspect is a safe read. Nothing is said about whether play requires user-gesture/autoplay permissions, what happens if multiple media elements exist, or what inspect returns.

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?

Two short sentences, front-loaded with the action list and followed by a scoping caveat; nothing is padding. It is perhaps too terse for the parameter surface it covers, but the wording itself is efficient.

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?

With 5 undocumented parameters, mutation-capable actions, and no output schema, the description leaves too much for the agent to infer: which element index is targeted, whether time is seconds, and what inspect returns (track list?). It is well short of what this tool's complexity requires.

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% across 5 parameters, so the description carries the full burden and largely fails. It implies the action enum and hints at seek, but never explains tabId, frameId, index (which media element?), or that time is the seek target and is required for seek.

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 verb set (inspect, play, pause, seek) against a specific resource (HTML5 media elements and text tracks), which is clearly distinct from nearby siblings such as firefox_inspect or firefox_screenshot. It doesn't explicitly contrast with siblings, but the resource is unambiguous.

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 second sentence usefully scopes the tool to browser media elements rather than private video APIs, which implies when it will and won't work. However, there is no guidance on prerequisites (a tab actually playing media), on when to use inspect versus the mutating actions, or on alternatives.

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