Read Media File

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

Description fully aligns with annotations (readOnlyHint=true). Adds critical behavioral details not in annotations: base64 encoding, MIME type, image/audio vs embedded resource handling, and directory restriction.

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, front-loaded sentences. Every clause adds value: base64, MIME type, file type distinction, directory restriction. No waste.

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 exists and is not described, which is fine. For a 1-parameter tool with good description and annotations, it covers all essentials. Lacks mention of size limits or encoding edge cases.

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?

Only 1 parameter (path) and schema coverage 0%, but description compensates by stating the expected file types and behavior. A bit more detail on path format (absolute/relative) would make it 5.

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?

Verb 'Read', resource 'media file', with specific behavior (base64, MIME type, image/audio vs other). Distinguishes from siblings read_file and read_text_file by targeting media content.

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?

Clearly says 'Only works within allowed directories' which implies a precondition. However, no explicit guidance on when to use this vs read_file vs read_text_file for non-media files or when format matters.

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