meta-mcp

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

With no annotations provided, description carries full burden and successfully discloses critical behavioral traits: destructive nature ('irreversible') and operational constraints ('Rate limited to 100 deletions per 24 hours'). Lacks auth requirements or error state details.

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 with zero waste: purpose declaration, safety warning, and rate limit—each earning its place. Information is front-loaded with the action clearly stated first.

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 single-parameter destructive operation without output schema, description adequately covers essential safety and operational context. Could be improved by mentioning return value (success indicator) or permission requirements, but sufficiently complete for agent selection.

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% (post_id fully documented), establishing baseline 3. Description implies the target resource but does not add syntax details, examples, or constraints beyond what the schema provides.

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?

Description opens with specific verb 'Delete' and resource 'Threads post', clearly distinguishing from Instagram tools (ig_*) and other Threads operations like replies or publishing. Scope is unambiguous.

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?

Provides implicit guidance through 'irreversible' warning, cautioning against casual use, but lacks explicit when-to-use criteria or comparisons to siblings like threads_hide_reply (though no direct alternative for post deletion exists).

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