ig_publish_photo

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action 'Publish' and the connected account, but does not explain side effects, permissions, rate limits, async behavior, or what happens on failure. This is a minimal mutation description with little operational transparency.

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 one sentence with active voice, no filler, and the core action is front-loaded. Every word contributes to the meaning, making it concise and easy to parse.

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 two-parameter tool, this is near-minimal but missing meaningful operational context: no mention of what the call returns, no note about asynchronous media processing, and no acknowledgement of the optional caption. The image_url requirement is covered by the schema, so the description is adequate but not fully complete.

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 only 50%: image_url has a schema-level description, but caption is completely undocumented. The tool description adds no parameter-level meaning beyond the schema, so the optional caption parameter remains unclear for an agent. With half the schema undocumented, the description should compensate but does not.

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 uses a specific verb ('Publish'), a precise resource ('a single photo'), and a target ('the connected Instagram Business account'). This clearly differentiates the tool from siblings like ig_publish_video and ig_publish_carousel while keeping the Instagram Business scope explicit.

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 use for publishing a single photo, but it does not explicitly state when to use this tool instead of alternatives such as ig_publish_video or ig_publish_carousel. There are no conditions, exclusions, or sibling tool references, leaving the agent to infer the appropriate selection context.

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