meta-mcp

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to mention whether this creates a publishing container (suggested by existence of threads_get_container_status sibling), whether the operation is synchronous or asynchronous, or what success/failure looks like. Critical gaps for a mutation tool.

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 consists of two efficient sentences: the first establishes the core purpose, the second enumerates key capabilities. No filler text; every word earns its place. Appropriately sized for the complexity.

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 100% schema coverage, basic parameter needs are met. However, for a publishing tool with no output schema and no annotations, the description lacks important context about return values (post ID vs container ID) and the asynchronous nature implied by sibling tools. Adequate but incomplete.

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 schema adequately documents all parameters. The description lists supported features ('topic tag, quote post, alt text, and spoiler flag') but adds no semantic meaning beyond what the schema already provides. Baseline 3 is appropriate given schema completeness.

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') and resource type ('image post') for the Threads platform. It effectively distinguishes from siblings like threads_publish_text, threads_publish_video, and threads_publish_carousel by specifying 'image post'.

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?

While the tool's purpose is clear from the name and description, there is no explicit guidance on when to use this versus threads_publish_carousel for single images, or prerequisites like checking publishing limits (threads_get_publishing_limit exists as a sibling). Usage is implied but not stated.

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