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 mentions case-sensitivity but doesn't disclose other behavioral traits like error handling, authentication needs, rate limits, or what happens when no object is found. The description is minimal beyond parameter documentation.

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. The parameter documentation is well-structured with clear bullet points. Every sentence earns its place, though the formatting with 'Args:' could be slightly 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 tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description does well on parameters but lacks behavioral context. It doesn't explain return values, error conditions, or usage scenarios. Given the complexity, it's adequate but has clear gaps in 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 fully compensate. It provides detailed semantics for all 4 parameters: explains what 'attack_id' is used for, lists all valid values for 'stix_type' and 'domain', and clarifies the purpose of 'include_description' with its default. 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 specific action ('Get object') and resource ('by ATT&CK ID'), with explicit case-sensitivity noted. It distinguishes from sibling tools like 'get_object_by_stix_id' and 'get_objects_by_name' by focusing on ATT&CK ID lookup rather than STIX ID or name-based searches.

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. With many sibling tools available (e.g., 'get_object_by_stix_id', 'get_objects_by_type'), the description doesn't explain scenarios where ATT&CK ID lookup is preferred or prerequisites for use.

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