Read Media File

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

Annotation already indicates readOnlyHint=true. Description adds behavioral details: returns base64 and MIME type, and restricts to allowed directories. Does not cover potential error conditions or size limits, but sufficient for basic transparency.

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 concise sentences, front-loaded with action and output. No unnecessary words; every sentence provides value.

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?

Output schema exists, so return value details are not required. Description covers purpose, output, and a key constraint. Missing error handling or file type specifics, but adequate for a simple tool.

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?

Single parameter 'path' with 0% schema description coverage. Description does not clarify path format, allowed directories, or constraints. Fails to compensate for missing schema documentation.

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 'Read an image or audio file' with specific verb and resource, and describes output (base64 encoded data and MIME type). Distinguishes from siblings like read_file or read_text_file by focusing on media types.

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?

Provides a constraint ('Only works within allowed directories') but no explicit guidance on when to use this tool versus alternatives like read_file. Implies media-specific use but lacks direct comparison.

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