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 must fully disclose behavior. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't clarify if it's a lookup, search, or list function. It lacks details on output format, pagination, error handling, or any constraints like rate limits or authentication needs, leaving significant gaps for an agent.

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 appropriately sized and front-loaded with the core purpose in the first line. The parameter explanations are clear and efficient, with no redundant sentences. However, the structure could be improved by integrating usage context rather than just listing args.

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, 0% schema coverage, and no output schema, the description does a fair job by explaining parameters and the basic purpose. However, it lacks details on return values, error cases, or behavioral traits, making it incomplete for a tool with three parameters in a complex domain like STIX/ATT&CK.

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 0%, so the description compensates by explaining all three parameters: 'mitigation_stix_id' (to check techniques), 'domain' (with valid values: 'enterprise', 'mobile', or 'ics'), and 'include_description' (default behavior). This adds meaningful context beyond the bare schema, though it doesn't detail 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 verb ('Get') and resource ('techniques mitigated by mitigation'), making the purpose understandable. It distinguishes from siblings like 'get_mitigations_mitigating_technique' by focusing on techniques rather than mitigations, though it doesn't explicitly name this distinction. The title is null, so the description carries the full burden and does so adequately.

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. It doesn't mention sibling tools like 'get_mitigations_mitigating_technique' (which has an inverse relationship) or explain specific contexts where this query is appropriate. The description only lists parameters without usage context.

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