⚠️ Send image

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

Beyond annotations (destructiveHint=true, etc.), the description adds important behavioral context: 'image is immediately and PUBLICLY visible', describes idempotencyKey conflict behavior, and dryRun preview. This informs the agent of real-world consequences.

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?

Three sentences with critical warning first, then process, then alternatives. Every sentence is essential and well-organized.

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 no output schema and 5 parameters, the description covers all necessary context: warnings, prerequisites, alternative tool, user confirmation, and parameter nuances. Sufficient for an agent to invoke correctly.

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 baseline is 3. The description adds context about image_id needing prior upload and idempotencyKey potentially causing conflict errors. However, it does not add new meaning for most parameters beyond schema descriptions.

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 'Sends an IMAGE ... to a chat on behalf of the account.', specifying the verb (send), resource (image), and destination (chat). It also distinguishes from sibling tool messenger_post_send_message by noting that tool is for text.

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?

Explicitly describes a two-step process: upload first then call this tool. Tells when to use alternatives ('For text, use messenger_post_send_message') and instructs to 'Confirm sending with the user.' Provides clear context for usage.

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