instagram_post_album

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

With no annotations, the description carries full burden but does not disclose behavioral aspects such as validation of media count/format, required permissions, rate limits, or what happens on errors, only listing parameters.

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 concise: a one-sentence purpose followed by a parameter list. No unnecessary words, though the parameter explanations could be integrated more tightly.

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 6 parameters and the existence of an output schema, the description covers the main purpose and parameter semantics adequately but misses behavioral details and constraints beyond the 2-10 range mentioned upfront.

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 0%, so the description adds moderate value by explaining parameters like 'Comma-separated hashtags' and 'Set True to disable comments', but lacks details on formats for image_paths_or_urls and constraints for mentions/location_name.

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 action ('Post') and resource ('carousel album') with the range '2-10 photos/videos', distinguishing it from single-media posts among sibling tools like instagram_post_photo and instagram_post_video.

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?

It implies usage for multiple media items but lacks explicit mention of when to use this tool versus alternatives like instagram_post_photo/video, and does not provide when-not-to-use conditions or exclusions.

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