MITRE ATT&CK 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. It mentions the tool 'gets' data (implying read-only), but doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what format/output to expect. The description lacks behavioral context beyond the basic operation, which is insufficient for a tool with no 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 perfectly structured and concise. The first sentence states the purpose clearly, followed by a well-formatted 'Args:' section with bullet-point parameter explanations. Every sentence earns its place, with zero redundant information. The formatting makes it easy to scan and understand.

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 3 parameters with 0% schema coverage and no output schema, the description does a good job explaining parameters but lacks context about the tool's behavior and output. It doesn't describe what 'tactics' means in the MITRE ATT&CK framework, what the return format looks like, or any error conditions. For a lookup tool with no annotations, this leaves significant gaps in understanding how to effectively use it.

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?

With 0% schema description coverage, the description must fully compensate. It provides clear semantics for all three parameters: 'technique_stix_id' is explained as 'Technique STIX ID to find associated tactics for', 'domain' specifies allowed values ('enterprise', 'mobile', or 'ics'), and 'include_description' clarifies its boolean nature and default. This adds substantial value beyond the bare schema, though it doesn't explain STIX ID format or domain implications.

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 tool's purpose: 'Get tactics associated with a technique' - a specific verb ('Get') and resource ('tactics') with a clear relationship ('associated with a technique'). It distinguishes from siblings like 'get_all_tactics' (which retrieves all tactics without filtering) and 'get_tactics_by_matrix' (which filters by matrix rather than technique). However, it doesn't explicitly mention what 'tactics' refers to in the MITRE ATT&CK context.

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 sibling tools like 'get_techniques_by_tactic' (reverse relationship) or 'get_all_tactics' (unfiltered list), nor does it specify prerequisites or appropriate contexts. The only implied usage is needing a technique STIX ID, but this is stated as a parameter requirement rather than usage guidance.

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