get_audio_files

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

There are no annotations to describe safety or side effects, and the description only says 'List all WAV audio files.' It does not explicitly state that the operation is read-only, nor does it disclose any permissions or potential side effects. The description carries the full burden here and falls short.

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, clear sentence with no unnecessary words. It effectively conveys the tool's purpose without verbosity.

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?

Given the tool's simplicity (no parameters, no output schema, and a straightforward list operation), the description is complete. It tells the agent exactly what the tool does, which is sufficient for calling it correctly.

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 tool has no parameters, so the baseline score is 4. The description does not need to add parameter meaning because there is nothing to describe.

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 verb 'List' and the resource 'all WAV audio files generated by the Gemini TTS MCP.' It is specific about the tool's scope and implicitly distinguishes it from the sibling tool generate_speech, which creates such files.

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 does not explicitly mention when to use this tool versus the sibling generate_speech. While the function name and description make it obvious that this lists files and the sibling creates them, there is no explicit guidance or condition for choosing this tool over the alternative.

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