MITRE ATT&CK 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 mentions the domain parameter and include_description flag but doesn't describe what 'getting all groups' entails - whether this returns a complete list, if there's pagination, what format the output takes, or any rate limits/authentication requirements. For a tool with no annotation coverage, this leaves significant behavioral questions unanswered.

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 efficiently structured with a clear purpose statement followed by parameter documentation. Both sentences earn their place by providing essential information. While it could be slightly more detailed, there's no wasted verbiage or redundancy in the current formulation.

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 complexity of querying threat actor groups, no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It doesn't explain what constitutes a 'threat actor group' in this context, what fields are returned, how many groups might be expected, or any limitations of the 'get all' operation. For a tool with rich sibling alternatives, this leaves too much context undefined.

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 description provides basic parameter information in the Args section, explaining what 'domain' represents and what 'include_description' controls. However, with 0% schema description coverage, this only partially compensates - it doesn't explain the significance of the domain choices ('enterprise', 'mobile', 'ics') or what the description output actually contains. The parameter documentation is present but incomplete.

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 ('all threat actor groups in the MITRE ATT&CK framework'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_groups_by_alias' or 'get_groups_using_technique', which would require more specific scoping language.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_groups_by_alias' or 'get_groups_using_technique'. The description only states what the tool does, not when it's appropriate or what distinguishes it from other group-related tools in the sibling list.

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