audio-to-markdown

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool converts audio to markdown with transcription, but lacks details on permissions needed, rate limits, error handling, or what 'if possible' implies (e.g., supported formats, transcription accuracy). For a tool with no annotations, this leaves significant gaps in understanding its operation and 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 description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core action ('Convert an audio file to markdown') and adds a useful qualifier ('including transcription if possible'). Every part earns its place, making it highly concise and well-structured.

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 complexity (audio processing and transcription) and lack of annotations and output schema, the description is incomplete. It doesn't explain return values (e.g., markdown content format), error cases, or behavioral details like supported audio formats. For a tool with no structured data to rely on, this leaves the agent under-informed about how to use it effectively.

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 description adds no parameter-specific information beyond what the input schema provides. The schema has 100% coverage with a clear description for 'filepath' as the 'Absolute path of the audio file to convert.' Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate with additional semantics like file format requirements or path examples.

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 tool's purpose: 'Convert an audio file to markdown, including transcription if possible.' It specifies the verb ('convert'), resource ('audio file'), and outcome ('to markdown'), distinguishing it from siblings that convert other file types (e.g., pdf-to-markdown). However, it doesn't explicitly differentiate from siblings beyond the resource type, such as by noting unique features like audio-specific transcription.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'including transcription if possible,' which hints at a capability, but doesn't specify prerequisites (e.g., file format support), exclusions, or direct comparisons to siblings like youtube-to-markdown for audio from videos. Without explicit when/when-not instructions, it leaves usage ambiguous.

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