upload_image

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

Beyond annotations, the description details that the tool reads a local file, uploads it as a blob, returns a blob descriptor and alt text, requires authentication, and is rate-limited. No contradictions with 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?

The description is concise (4 sentences, ~80 words) and front-loaded with the purpose. Every sentence contributes meaningful information without redundancy.

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?

Given the presence of an output schema and complete input schema, the description provides full context: what to do with the output, authentication requirements, rate limiting, and sibling tool differentiation.

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%, so the input schema fully describes both parameters. The description adds minimal semantic value beyond the schema, only slightly elaborating on filePath in the general tool description.

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 uploads an image file to AT Protocol for use in posts and profiles. It specifies supported formats, size limit, and distinguishes from sibling tools like upload_video and analyze_image.

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 provides explicit usage guidance: use this for images in posts/profiles, use upload_video for videos. It also explains how to use the output (pass image.blob to create_post, update_profile, or analyze_image).

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