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. It states the tool retrieves matrices but doesn't disclose behavioral traits like whether it's a read-only operation (implied by 'Get'), potential rate limits, authentication needs, or what the output format looks like (e.g., list of objects, JSON structure). For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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: the first sentence states the core purpose, followed by a structured 'Args:' section. There's no wasted text, and each part adds value. It could be slightly improved by integrating the parameter details more seamlessly, but overall it's efficient and well-organized.

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 tool's moderate complexity (2 parameters, no output schema, no annotations), the description is partially complete. It covers the purpose and parameters adequately but lacks context on usage guidelines, behavioral transparency, and output details. For a read operation in a crowded toolset, more guidance on when and how to use it would enhance completeness.

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 adds meaningful context for both parameters: it explains 'domain' accepts specific values ('enterprise', 'mobile', or 'ics') and clarifies 'include_description' controls output inclusion with a default. With 0% schema description coverage, this compensates well by providing essential semantics. However, it doesn't detail parameter interactions or edge cases (e.g., what happens if an invalid domain is provided).

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 all matrices in the MITRE ATT&CK framework' - a specific verb ('Get') and resource ('matrices'). It distinguishes from siblings like 'get_all_tactics' or 'get_all_techniques' by focusing on matrices. However, it doesn't explicitly differentiate from similar-sounding tools like 'get_tactics_by_matrix' or 'generate_layer', which might be related but serve different purposes.

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 (e.g., 'get_all_tactics', 'get_all_techniques', 'get_tactics_by_matrix'), there's no indication of whether this is a broad overview tool, a prerequisite for others, or how it relates to domain-specific queries. The absence of usage context leaves the agent guessing about appropriate scenarios.

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