meta-mcp

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. While 'Publish' indicates a write operation, the description omits critical behavioral details: whether publishing is synchronous or asynchronous (relevant given the threads_get_container_status sibling), return value structure, error handling, or idempotency guarantees.

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 a single, efficient sentence with zero redundancy. The constraint '2-20 images/videos' is front-loaded and essential for distinguishing this from other publish tools.

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 this is a complex publishing operation with no output schema and no annotations, the description is insufficient. It fails to disclose what the tool returns (likely a container ID requiring status polling via threads_get_container_status), rate limits, or side effects like notifications generated.

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 description coverage is 100%, establishing a baseline of 3. The description reinforces the items array constraints (2-20) but adds no semantic nuance beyond the schema, such as explaining the relationship between quote_post_id and carousel items or alt_text best practices.

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 specific action ('Publish'), resource ('carousel post on Threads'), and unique constraint ('2-20 images/videos'). However, it does not explicitly differentiate from sibling tools like threads_publish_image or threads_publish_video, though the 2-20 constraint implies multi-media usage.

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?

The '2-20 images/videos' constraint implicitly signals when to use this tool versus single-media alternatives. However, there is no explicit guidance on when to choose this over threads_publish_image/video, nor any mention of prerequisites like authentication or media requirements.

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