Threads MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation ('Archive') but doesn't specify if this is reversible, requires permissions, affects thread visibility, or has side effects like notifications. The optional cascading behavior is mentioned but lacks detail on what 'child threads' entail or system impacts.

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—a single, front-loaded sentence that directly states the tool's function with an optional feature. There is no wasted wording, repetition, or unnecessary elaboration, making it efficient for an agent to parse.

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 complexity (a mutation with cascading options), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like reversibility, error conditions, or return values, leaving significant gaps for the agent to infer or handle incorrectly.

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%, so the input schema fully documents parameters (id and cascade). The description adds minimal value by implying the cascade parameter's effect ('optionally with children'), but doesn't provide additional semantics beyond what the schema states. This meets the baseline for high schema coverage.

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 action ('Archive') and resource ('a thread'), making the purpose evident. It distinguishes from deletion tools like delete_thread by specifying archival rather than permanent removal. However, it doesn't explicitly differentiate from sibling tools like update_thread that might have archival options, keeping it from a perfect score.

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. It doesn't mention prerequisites (e.g., thread must exist), exclusions (e.g., cannot archive already archived threads), or comparisons to tools like delete_thread or update_thread. This leaves the agent with minimal context for decision-making.

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