meta-mcp

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

Discloses critical blocking behavior ('Waits for video processing') which is essential given no annotations indicate long-running operations. However, missing auth requirements, error handling behavior, and idempotency guarantees since annotations are absent.

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 defines scope, second discloses blocking behavior. Front-loaded with action verb. No redundant phrases.

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?

Minimal but viable for a publishing tool. Mentions processing wait time but omits return value structure (despite no output schema), success/failure indicators, or prerequisite validation that would help an agent handle the response correctly.

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, so description appropriately relies on structured documentation rather than repeating parameter details. No additional semantic context (e.g., valid ranges for thumb_offset, URL requirements) added, warranting baseline score.

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') and resource ('Reel'), with parenthetical clarification '(short video)'. Distinguishes from siblings like ig_publish_photo/story/carousel by naming the specific content type, though could explicitly clarify difference from ig_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?

No guidance on when to use this vs. ig_publish_video (standard video posts) or prerequisites like business account verification. No mention of alternative publishing flows or rate limit considerations.

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