meta-mcp

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

No annotations provided, so description carries full burden. It mentions the media count limits but fails to disclose critical write-operation details: whether publishing is synchronous, what errors might occur, rate limits, or whether the operation is reversible. Slightly imprecise terminology referring to 'image_url or video_url' when schema uses a unified 'url' field with type discriminator.

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 no filler. Front-loaded with the core action and constraints. Every word serves a purpose.

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?

For a publishing tool with no annotations or output schema, the description lacks operational context. Missing: return value details (post ID?), error conditions, authentication scope, and platform-specific behaviors (e.g., alt_text only valid for images).

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 coverage is 100%, establishing baseline 3. Description reinforces the 2-10 item constraint and URL requirement, but inaccurately describes the schema structure as having separate image_url/video_url fields rather than a single 'url' field with a type enum. Does not elaborate on optional caption or location_id parameters.

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?

Clearly states it publishes a carousel/album post and specifies the 2-10 media item constraint. However, it does not explicitly differentiate this from sibling publishing tools like ig_publish_photo or threads_publish_carousel.

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?

States the quantity constraint (2-10 items) but provides no guidance on when to use this versus single-image publishing or other platforms. No mention of prerequisites like account requirements or media specifications beyond count.

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