meta-mcp

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

With no annotations provided, the description carries the full burden and successfully discloses the critical blocking behavior ('Waits for video processing'). However, it lacks details on failure modes, timeouts, or what the tool returns upon completion.

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?

Three sentences total with zero waste: sentence 1 states purpose, sentence 2 discloses blocking behavior, and sentence 3 lists key features. Perfectly front-loaded and efficient.

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 the rich input schema (7 params, 100% coverage) and lack of output schema, the description provides adequate completeness by covering purpose, blocking behavior, and feature support. Minor gap: does not describe return values or error conditions.

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?

With 100% schema description coverage, the baseline is 3. The description mentions four specific parameters (topic tag, quote post, alt text, spoiler flag) but does not add semantic meaning beyond the schema's descriptions (e.g., explaining how quote_post_id functions or reply_control options).

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 opens with a specific verb ('Publish') + resource ('video post') + platform ('Threads'), clearly distinguishing it from sibling tools like threads_publish_image and threads_publish_text.

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 phrase 'Waits for video processing' provides implicit behavioral guidance (synchronous blocking vs. async), but there is no explicit 'when to use this vs. alternatives' guidance or prerequisites mentioned.

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