meta-mcp

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

Adds valuable behavioral detail that it 'waits for video processing before publishing' (critical given sibling ig_get_container_status exists), but omits auth requirements, error scenarios, and side effects since no annotations are provided.

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: first establishes purpose, second discloses key blocking behavior. Efficiently front-loaded with no filler content.

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 4-parameter publishing tool despite missing output schema details, though could strengthen context by mentioning Instagram Business/Creator account requirements or distinguishing video specs from Reels.

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?

Input schema has 100% description coverage; description correctly omits redundant parameter details since schema fully documents video_url, caption, thumb_offset, and location_id.

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?

Specific verb 'Publish' with clear resource 'video' and scope 'Instagram feed' effectively distinguishes from siblings like ig_publish_reel, ig_publish_story, ig_publish_photo, and threads_publish_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?

Implies usage context through 'feed' specification but lacks explicit when-to-use guidance comparing to Reels/Stories alternatives or prerequisites like required Facebook Page connection.

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