ig_publish_image

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

Annotations already declare a non-destructive write (readOnlyHint=false, destructiveHint=false), lowering the bar. The description only adds the JPEG format constraint; it says nothing about publishing rate limits (a dedicated ig_publishing_limit sibling exists), the irreversibility of a published post, or the INSTA_PILOT_BLOB_TOKEN requirement for local paths.

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?

A single front-loaded sentence with zero waste, which is good structurally. However, it is arguably under-specified rather than concise for a six-parameter publishing operation.

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?

A mutation tool with no output schema, six parameters at 50% description coverage, and a sibling that exists specifically to check publishing limits. The description leaves an agent without enough context to invoke it correctly in edge cases (rate limits, account selection, token requirements).

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 only 50%: image, account and dry_run are documented in the schema, while caption, alt_text and location_id are not. The description adds nothing beyond restating the JPEG format for the image parameter, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Publica una foto') and adds a format constraint (JPEG), which implicitly separates it from the reel, carousel and story siblings. It does not explicitly name those siblings, so an agent must infer the distinction from the resource noun.

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?

No statement of when to use this tool versus ig_publish_reel, ig_publish_carousel, ig_publish_story, or the account-selection flow. The only implied guidance is that this is for photos, which is already implied by the name.

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