create_image_post

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

No annotations provided. The description does not disclose behavioral traits such as authentication needs, rate limits, error behaviors (e.g., invalid image URL), or the distinction between draft and published states beyond the publish parameter.

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?

Extremely concise, front-loading the core purpose. Every sentence is relevant, though more detail could be added without losing conciseness.

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?

For a creation tool with 5 parameters (1 required), no output schema, and no annotations, the description is incomplete. It omits return values, error handling, and explanation of non-obvious parameters like reply_control.

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 80% (4/5 parameters described). The description adds value by highlighting the publish parameter's effect, but does not add meaning for other parameters (e.g., reply_control lacks description entirely). Baseline 3 is appropriate.

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?

Clearly states it creates a Threads post with an image, distinguishing it from text/video posts. However, it does not explicitly contrast with create_carousel_post, which also involves images.

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?

Only mentions setting publish:true for immediate publishing, but provides no guidance on when to use this tool versus alternatives like create_text_post or create_carousel_post.

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