Threads MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete a container' implies a destructive, irreversible mutation, but it doesn't specify permissions required, whether deletion is permanent or recoverable, side effects (e.g., impact on child elements), or error conditions. For a destructive tool with zero annotation coverage, this is insufficient behavioral context.

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 extremely concise at three words, with zero wasted language. It's front-loaded with the core action and resource. Every word earns its place, making it efficient for quick scanning by an AI agent.

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 tool's destructive nature, lack of annotations, no output schema, and multiple sibling deletion tools, the description is incomplete. It doesn't clarify what a 'container' is, how deletion behaves, or differentiate it from similar tools. For a mutation tool in a complex environment, more context is needed to ensure correct usage.

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?

The input schema has 100% description coverage (the 'id' parameter is documented as 'Container ID'), so the schema does the heavy lifting. The description doesn't add any parameter-specific information beyond what's in the schema, but with only one parameter and high schema coverage, a baseline of 3 is appropriate. The score is 4 because the description is concise and doesn't create confusion, though it doesn't enhance parameter understanding.

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 'Delete a container' clearly states the action (delete) and resource (container), but it's vague about what a 'container' represents in this context and doesn't distinguish this tool from sibling deletion tools like delete_group, delete_progress, or delete_thread. It provides basic purpose but lacks specificity about the resource type.

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 description provides no guidance on when to use this tool versus alternatives. With sibling tools like delete_group, delete_progress, and delete_thread available, there's no indication of what differentiates a 'container' from these other resources or when deletion of one versus another is appropriate. No prerequisites, exclusions, or alternatives are mentioned.

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