instagram_post_photo

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

No annotations are provided, so the description must disclose behaviors. It notes that the tool creates a post (mutation) but omits critical details: authentication requirements, rate limits, error handling (e.g., invalid image URL), and what the tool returns (output schema exists but undescribed).

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 well-structured: a clear one-line purpose followed by a bulletized parameter list. It is efficient, though the phrase 'with FULL control' is slightly promotional but not overly verbose. Front-loading the purpose helps quick scanning.

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 complexity (9 parameters, no annotations), the description covers parameter semantics well but lacks information about return values (output schema exists but not mentioned), error handling, and prerequisites (e.g., authentication status, image size limits). It feels adequate but not comprehensive.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter's purpose and expected format (e.g., 'hashtags: Comma-separated hashtags to append', 'tag_users_in_photo: physically TAG in the image'). This adds significant value beyond the raw schema.

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 tool posts a photo to the Instagram feed, with 'FULL control' emphasizing customization. This distinguishes it from sibling tools like post_album, post_reel, or post_video, which handle different media types.

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 explicit guidance on when to use this tool vs. alternatives (e.g., post_album for multiple photos, post_video for video). The phrase 'with FULL control' implies advanced options but doesn't clarify prerequisites or scenarios to prefer other tools.

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