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. It states the action ('Get') but doesn't describe what 'Get' entails—whether it returns full group details, permissions required, error behavior for invalid identifiers, or response format. For a read operation without annotations, this leaves significant behavioral gaps.

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 sentence with zero wasted words. It's front-loaded with the core purpose and efficiently specifies the lookup mechanism. Every word earns its place without redundancy or unnecessary elaboration.

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 no annotations, no output schema, and a simple parameter structure, the description is incomplete. It doesn't address what the tool returns (e.g., group object structure), error conditions, or how it fits within the broader toolset (e.g., relationship to 'create_group' or 'update_group'). For a basic read tool, more contextual information would be helpful.

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%, with the parameter 'identifier' documented as 'Group ID or name'. The description adds no additional semantic context beyond this—it doesn't clarify format examples, case sensitivity, or uniqueness constraints. Baseline 3 is appropriate since the schema already provides adequate parameter documentation.

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 verb ('Get') and resource ('a group'), specifying it retrieves a group by ID or name. It distinguishes from siblings like 'list_groups' (which lists multiple groups) and 'get_ancestors' (which retrieves hierarchical data), but doesn't explicitly contrast with 'get_entity' which might have overlapping functionality.

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 when to choose 'get_group' over 'list_groups' for single-group retrieval, or how it differs from 'get_entity' which might also fetch groups. No prerequisites, exclusions, or contextual usage hints are provided.

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