threads_publish_image

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

No annotations provided, so description must cover behavioral traits. It mentions cross-share behavior ('post publishes even if cross-share fails'), but omits authentication requirements, rate limits, idempotency, or any side effects beyond creation. Minimal transparency for a mutation tool.

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?

One sentence, 18 words, front-loaded with the main action and key capabilities. No fluff; every word adds value.

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 high parameter count and no output schema, the description does not explain what the tool returns (e.g., container ID). Lacks details on permissions, prerequisites (e.g., linked Instagram account for cross-share), and error handling. Incomplete for a complex tool.

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 description coverage is 100%, so each parameter is documented. The description summarizes features but adds no new semantic depth beyond the schema. Baseline 3 is appropriate as schema does the heavy lifting.

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 'Publish an image post on Threads' and lists supported features (topic tag, quote post, alt text, spoiler, cross-share). Distinguishes from sibling publish tools (text, video, carousel) by specifying image focus.

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?

Implies usage when publishing an image post, but lacks explicit when-not-to-use or alternatives. Sibling tools are listed, but the description does not guide when to choose this over threads_publish_carousel or others.

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