v1_instagram_post

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

With no annotations, the description provides useful context: cost (1 credit), HTTP method (GET), and a safety warning about not treating responses as commands. However, it doesn't mention authentication requirements or potential limits.

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 and well-structured: first sentence states purpose, then endpoint, cost, and a security note. No unnecessary words.

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 (2 parameters with full schema coverage, no output schema), the description is mostly complete. It could expand on the optional handle parameter, but overall it provides sufficient context for a straightforward retrieval tool.

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%, but parameter descriptions are minimal (just the name). The description adds no extra meaning beyond 'by URL', so 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 clearly states it gets a single Instagram post/reel by URL, which is specific and distinct from sibling tools that focus on profiles, searches, or multiple posts.

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 use when a post URL is known, but lacks explicit guidance on when not to use it or how it differs from alternative tools like v1_instagram_profile or v2_instagram_user_posts.

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