Threads MCP Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Delete a group' implies a destructive, irreversible mutation, but it doesn't specify permissions required, side effects (e.g., what happens to child entities), error conditions, or response format. This is inadequate for a destructive operation with zero annotation coverage.

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 ('Delete a group') with no wasted words. It's front-loaded with the core action, though this brevity comes at the cost of completeness. Every word earns its place by conveying the essential purpose without fluff.

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, and no output schema, the description is incomplete. It doesn't address critical context like permissions, side effects, error handling, or what happens upon success. For a delete operation with no structured safety hints, this leaves significant gaps for an AI agent.

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 'Group ID'), so the baseline is 3. The description doesn't add any parameter-specific information beyond what the schema provides, but with only one parameter that's fully documented, this is acceptable. A score of 4 reflects that the description doesn't detract from the schema's 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 'Delete a group' clearly states the action (delete) and target resource (group), which is better than a tautology. However, it lacks specificity about what constitutes a 'group' in this context and doesn't differentiate from sibling tools like delete_container or delete_thread, which perform similar deletion operations on different resource types.

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., group must exist), exclusions (e.g., cannot delete groups with children), or related tools like delete_container or delete_thread for deleting other resource types. The agent receives no usage context beyond the basic action.

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