encode_file_to_base64

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

Discloses binary mode reading, base64 output, and absolute path restriction. Lacks mention of potential memory issues with large files, but covers key behaviors given no annotations.

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 sentences, front-loaded with purpose then detail. No superfluous content.

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?

Sufficient for a single-parameter tool with output schema. Does not mention error scenarios (e.g., missing file) but acceptable for simple encoding 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?

Schema provides 100% coverage with description for file_path. Description adds important constraint 'only absolute paths' beyond schema examples, adding value.

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 verb 'encode' and resource 'file to base64 string'. Differentiates from sibling 'decode_base64_to_file' by describing encoding direction.

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?

Implies usage for encoding files to base64. Mentions absolute path requirement for security, but no explicit when-not-to-use or alternatives beyond tool name.

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