ig_publish_photo

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

With no annotations, the description carries the full burden. It discloses the two-step process and the requirement for a publicly accessible URL. However, it omits details like authentication needs, rate limits, or that it only works with Instagram Business accounts, which are critical for safe invocation.

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?

The description is two sentences, front-loading the purpose. Every word contributes value: 'Publish a photo to Instagram' is the core, and the second sentence explains the process and key constraint. No redundancy or filler.

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?

The description lacks crucial information for a two-step process: what is returned after the first step (container ID?), how to poll for status, and what success looks like. Without an output schema, the agent is left blind. Also missing context about required account type (Business/Creator) and potential errors.

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%, providing descriptions for all parameters. The description supplements by reinforcing the image_url requirement but adds no new per-parameter semantics beyond what the schema already states. Baseline of 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?

The description clearly states the verb 'publish' and resource 'photo to Instagram', and distinguishes from siblings by specifying 'photo' and mentioning the two-step process. It also notes the requirement for a public HTTPS URL, which adds specificity.

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?

The description implies usage for publishing a single photo but does not explicitly compare to alternative tools like ig_publish_carousel, ig_publish_reel, or ig_publish_story. No when-not guidance is provided, leaving the agent to infer from the tool name alone.

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