publish_media

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

No annotations are provided, so the description carries full burden. It mentions 'upload and publish' which implies a write/mutation operation, but doesn't disclose critical behavioral traits like authentication requirements, rate limits, whether the action is reversible, error conditions, or what happens on success. The description adds minimal context beyond the basic action.

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, efficient sentence that front-loads the core purpose. Every word earns its place - 'Upload and publish' establishes the action, 'image or video to Instagram' specifies the resource and platform, and 'with caption and optional location' highlights key parameters without redundancy.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after publishing (success response, media ID returned, error handling), authentication requirements, or platform-specific constraints. The 100% schema coverage helps with parameters, but behavioral and output context is missing.

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 the schema already documents all parameters thoroughly. The description adds marginal value by mentioning 'caption and optional location' which echoes the schema, but doesn't provide additional semantic context like format requirements beyond what's in the schema descriptions.

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 specific action ('Upload and publish'), the resource ('an image or video to Instagram'), and the key parameters ('with caption and optional location'). It distinguishes this tool from siblings like publish_carousel and publish_reel by specifying it's for single image/video posts, not carousels or reels.

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 context (publishing to Instagram) but doesn't explicitly state when to use this tool versus alternatives like publish_carousel or publish_reel. It mentions optional parameters but provides no guidance on prerequisites, timing, or constraints beyond what's in the schema.

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