publish_image

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

With no annotations, the description carries full responsibility for disclosing side effects. It only says 'publish', which implies a post creation, but does not mention required authentication, irreversible actions, potential failures, or how the Cloudinary URL is processed. The contradictory 'local image' vs 'Cloudinary-hosted URL' adds further opacity.

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 a single concise sentence, front-loaded with the key action. However, it omits critical details and is somewhat awkwardly phrased, but no unnecessary words are present.

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?

Given the tool has no output schema, no annotations, and only two parameters, the description should provide clear context about workflows, expected inputs, and success/failure behavior. It does none of these, leaving the agent with insufficient information to invoke the tool reliably.

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?

The schema has two parameters (filename, caption) with zero coverage from the description. The description does not explain what 'filename' refers to (local path? Cloudinary public ID?) or how 'caption' is used. The mention of 'local image' and 'Cloudinary-hosted URL' does not map clearly to either parameter, so an agent cannot infer parameter meanings.

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') and target ('Instagram'), but the phrase 'local image ... using a Cloudinary-hosted HTTPS image URL' is contradictory and unclear about the actual input source. It also does not distinguish itself from the sibling tool 'post_to_instagram', which likely serves a similar purpose.

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 guidance is provided on when to use this tool relative to siblings like 'post_to_instagram' or 'test_instagram_connection'. There is no mention of prerequisites, alternative scenarios, or why one would pick this tool over others.

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