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. While it states what the tool does, it doesn't describe important behavioral aspects: whether this is a lookup/read-only operation, what happens when no match is found, what format the attack ID is returned in, or any error conditions. The description is minimal and lacks operational context.

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 concise with a clear purpose statement followed by parameter explanations. However, the formatting with 'Args:' heading is somewhat redundant since parameters are already documented in the schema. The structure is functional but could be more integrated.

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?

For a lookup tool with no annotations and no output schema, the description is incomplete. It doesn't explain what format the attack ID is returned in (string, object, etc.), what happens on failure, or provide any examples. Given the rich ecosystem of ATT&CK tools and the importance of ID mapping in security contexts, more operational context would be valuable.

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 compensates well by explaining both parameters: 'stix_id: STIX ID to find associated ATT&CK ID for' and 'domain: Domain name ('enterprise', 'mobile', or 'ics')'. It provides the exact enum values for domain and clarifies the relationship between STIX ID and ATT&CK ID. This adds significant value beyond the bare schema.

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 attack ID for given stix ID' - this is a specific verb ('Get') + resource ('attack ID') with a clear input ('stix ID'). However, it doesn't distinguish this tool from its sibling 'get_object_by_stix_id' which appears to serve a similar lookup function but returns a full object rather than just an ATT&CK ID.

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. With many sibling tools that perform various ATT&CK-related lookups (including 'get_object_by_stix_id' and 'get_object_by_attack_id'), there's no indication of when this specific ID-mapping tool is preferred over other retrieval methods.

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