convert_base64

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

The description reveals that conversion runs locally and on-device via anydoc, which is a meaningful behavioral trait given no annotations. However, it does not mention return format, error handling, or other side effects, leaving some behavioral aspects undisclosed.

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 two sentences, starts with the core action, and each sentence contributes distinct value: what it does, when to use, and where it runs. There is no wasted or redundant wording.

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?

For a tool with 3 parameters and no output schema, the description covers purpose, usage context, and a behavioral note. It does not explicitly describe the return value, but the conversion to Markdown implies the output. Given the simplicity, it is reasonably complete for selection and invocation.

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 input schema already provides complete descriptions for all 3 parameters (100% coverage), so the description adds little beyond schema. It mentions 'base64' and 'filename' but does not clarify parameter usage or dependencies beyond what the schema states.

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 converts base64 document bytes to Markdown locally, using a specific verb and resource. It distinguishes itself from path-based sibling tools by emphasizing the base64 input context.

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 gives explicit guidance on when to use the tool: when file content is already in context and a filesystem path cannot be passed. It implies when not to use it but does not name alternative tools directly, though siblings are visible in context.

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