meta-mcp

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

No annotations provided, so description carries full burden. Successfully discloses the ephemeral 24-hour lifecycle trait, but omits operational details like whether media_url requires pre-upload to IG servers, rate limits, or async publishing status checks.

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?

Two sentences with zero waste. Front-loaded with the core action ('Publish a Story'), followed immediately by format parenthetical, then the critical behavioral constraint (24-hour expiry). Every word earns its place.

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?

Adequate for a 2-parameter publishing tool but missing prerequisites typical for IG APIs (e.g., media container requirements, Business Account eligibility) and error conditions. No output schema exists, though description doesn't address what success/failure looks like.

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 has 100% description coverage, establishing baseline 3. Description reinforces the image/video options but adds no Story-specific constraints (e.g., 9:16 aspect ratio, video duration limits) or format validation details beyond what the schema provides.

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?

States specific action (Publish) + resource (Story) + format constraints (image or video). The 24-hour disappearance trait clearly distinguishes this ephemeral format from sibling publishing tools like ig_publish_photo or ig_publish_reel.

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?

Implies usage context through the 24-hour disappearance note (ephemeral vs permanent content), but lacks explicit comparison to sibling publishing tools or guidance on when to choose Stories over feed posts, reels, or carousels.

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