Gemini Audio MCP

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

Discloses execution mechanism (system default player like 'afplay') but omits critical behavioral details like blocking vs. async behavior, error handling, or supported formats since no annotations exist.

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?

Single, efficient sentence that front-loads the verb and mechanism; no wasted words.

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?

Adequate for a simple single-parameter tool; explains the playback mechanism sufficiently given no output schema exists to document.

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?

With 100% schema coverage, baseline is met; description reinforces 'local' constraint but adds no substantial semantic layer beyond the schema's 'absolute path' definition.

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?

Clearly states it plays local audio files using the system default player, effectively distinguishing from sibling generation tools (generate_music, generate_sfx, etc.).

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?

Implies usage for existing files via 'local audio file,' but lacks explicit when/when-not guidance contrasting with the generation siblings.

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