Download a single-image Instagram post at original full resolution. Use download_carousel instead if the post has multiple slides.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public Instagram single-image post URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the download action and resolution but omits key behavioral details such as output format (URL or binary), authentication requirements, rate limits, or side effects.
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 two sentences with no extraneous information. Every word contributes to clarity and purpose.
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's simplicity (one parameter, no output schema), the description covers the essential purpose and usage. However, it could be improved by describing the output format or return value.
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 100% coverage for the single parameter (url), so the description adds no significant meaning beyond what is already documented. Baseline 3 is appropriate.
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 explicitly states the action (download), the resource (single-image Instagram post), and the resolution (original full resolution). It also distinguishes from the sibling tool download_carousel by specifying when to use that alternative.
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 clearly indicates when to use this tool (single-image posts) and when not to (use download_carousel for multiple slides). However, it does not address other potential alternatives or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear distinct purposes; however, engagement_calculator and engagement_health_check have overlapping functionality, both dealing with engagement metrics, which could cause confusion.
Majority of tools follow a verb_noun pattern (e.g., download_photo, search_hashtags), but two tools start with nouns (engagement_calculator, engagement_health_check), breaking the consistency.
16 tools cover a wide range of Instagram-related tasks without being excessive. Each tool serves a specific purpose relevant to the toolkit's domain.
The toolkit covers downloading, engagement analysis, content generation, and hashtag research. Missing features like posting or advanced profile analytics are minor gaps for an analytical toolkit.