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 the full burden of behavioral disclosure. It mentions case-sensitivity, which is useful, but lacks critical details: it doesn't specify what happens if the STIX ID isn't found (e.g., returns null or error), whether it's a read-only operation, any rate limits, or authentication requirements. For a lookup tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 well-structured and appropriately sized. It starts with a clear purpose statement, followed by a bullet-point-style 'Args' section that efficiently explains each parameter. Every sentence adds value without redundancy, though it could be slightly more front-loaded by integrating parameter details into the initial sentence.

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 decent job but has gaps. It explains parameters well but doesn't describe the returned 'object' format, error handling, or how it differs from similar tools. For a lookup tool in a complex domain (ATT&CK/STIX), more context on output structure and use cases would improve 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?

Schema description coverage is 0%, so the description must compensate. It adds meaningful context for all three parameters: 'stix_id' is an 'ATT&CK ID to find associated object for', 'domain' specifies allowed values ('enterprise', 'mobile', or 'ics') with a default, and 'include_description' explains its effect on output. This goes beyond the bare schema, though it doesn't detail the 'object' structure returned.

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 object by STIX ID (case-sensitive)'. It specifies the verb 'Get' and the resource 'object', and distinguishes it from siblings like 'get_object_by_attack_id' by focusing on STIX IDs. However, it doesn't explicitly differentiate from 'get_objects_by_content' or 'get_objects_by_name', which are similar lookup tools, so it's not a perfect 5.

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 when to choose it over sibling tools like 'get_object_by_attack_id' (for ATT&CK IDs) or 'get_objects_by_name' (for name-based lookups). The only implicit usage hint is the case-sensitivity note, but this is insufficient for clear decision-making.

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