⚠️ Send image

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

Warns that image is immediately and publicly visible to the other party, adding behavioral context beyond annotations (destructiveHint=true). Could mention if the action is reversible.

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 concise sentences with key information front-loaded: action, prerequisite, warning, and sibling reference. No unnecessary text.

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?

No output schema and description does not indicate what the tool returns (e.g., success status, message ID). Leaves some ambiguity about outcome.

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 all parameters are documented. Description repeats the two-step process already implied by image_id parameter description, adding no new semantic detail.

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?

Explicitly states sending an image to a chat using an uploaded image_id. Clearly distinguishes from sibling tool 'messenger_post_send_message' which 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?

Provides clear two-step process: first upload via messenger_upload_images, then call this tool. Explicitly states when to use alternative (text messages) and advises confirming with user.

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