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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds meaningful context that it 'processes in the browser' and 'uses more credits per run than Document/Image/Scanner workspaces,' which are operational traits not evident from the schema or tool name. It also clarifies workspace inclusion and pricing, helping agents understand the tool's constraints.

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 purpose is front-loaded in the first phrase, making the core function immediately clear. The subsequent sentences about credits and workspaces provide useful context, though they occupy a significant portion of the description and could be condensed. It is generally concise but not maximally so.

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?

The description covers the tool's purpose and important operational constraints (credits, workspace access). However, with no output schema and no parameters, it does not explain how the OGG file is supplied, what the MP3 output looks like, or any file size/format limitations. This leaves gaps for an agent attempting to invoke the tool correctly beyond knowing the conversion intent.

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 zero parameters, and the schema's properties object is empty, so the baseline for parameter semantics is 4. The description does not need to explain any parameters, and it does not introduce any missing parameter context.

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 opens with 'OGG to MP3 — Convert OGG Vorbis audio to MP3 format,' which clearly states a specific verb (convert), resource (OGG Vorbis audio), and output (MP3). This distinguishes it from sibling tools like mio_video_to_mp3 or mio_audio_converter by the specific input format.

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 implies usage context: use this tool when you need to convert OGG Vorbis audio to MP3. However, it does not explicitly discuss when to prefer this over alternative converters, nor does it mention any exclusions or prerequisites beyond credit/workspace restrictions. The credit information is more about feasibility than usage guidance.

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