resolve_blobs

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

Explains the transformation from temporary blob URL to base64 data URI, but given no annotations, could further disclose limitations (e.g., size caps, cross-origin restrictions, no side effects like destructive behavior).

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 with zero filler: one sentence states purpose, the second adds context about blob URLs and the conversion result.

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?

Adequately describes the problem and solution; lacks output format details (e.g., return structure or error handling) but reasonable for a simple conversion tool without output schema.

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 coverage is 100% (all parameters documented in schema), so baseline is 3; description does not add extra parameter details beyond schema.

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?

Describes the specific action 'resolve blob: URLs to downloadable base64 data', explains what blob URLs are, and clearly distinguishes from any sibling tool (no other tool does this conversion).

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 context on when to use (encountering blob URLs from Telegram, WhatsApp, Discord that cannot be downloaded directly), but lacks explicit when-not-to-use or alternative tool names.

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