publish_image

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

No annotations provided, so description carries full burden. Discloses that image_url must be publicly accessible HTTPS URL, caption max 2200 chars, and that the two-step Graph flow is handled internally. Misses potential side effects like error handling or rate limits, but covers key behavioral traits.

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, no wasted words. Front-loaded purpose, then constraints, then implementation detail. Efficient and to the point.

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?

Despite having an output schema (not shown), description does not mention return values. However, for a mutation tool with 3 parameters, it covers essential constraints and distinguishes from 20+ sibling tools. Missing explanation of the optional account parameter.

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 0%, so description must compensate. Explains image_url requirements (public HTTPS) and caption length limit. However, the 'account' parameter is left unexplained, which reduces completeness.

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 publishes a single image to the feed, differentiating it from siblings like publish_video, publish_carousel, etc. The verb 'publish' and resource 'single image' are specific.

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 key constraints (public URL, caption limit) and notes internal two-step flow, but lacks explicit guidance on when to use this tool versus other publishing tools (e.g., publish_carousel or publish_story). Usage context is implied but not explicitly stated.

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