MITRE Gap Analysis

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds the behavioral nuance that results are 'prioritized' by weakest coverage, which is meaningful beyond the annotations, and states it's optional to filter by tactic — adding useful behavior context without contradicting the annotations.

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?

One tight sentence that names the output, explains its purpose, and notes an optional filter. Zero filler, front-loaded with the core purpose. Every element earns its place.

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?

With an output schema present and full annotation coverage, the description need not explain return values or safety. It explains the functional purpose and the tactic-filter option, which is sufficient for a straightforward read-only list tool with 2 well-documented parameters.

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 100% schema description coverage, the schema already documents both parameters well (limit with defaults/max, tactic with example). The description doesn't add new param detail beyond implying tactic is optional, but given full schema coverage, the baseline of 3 is appropriate — the structured field carries the burden and does so adequately.

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 produces a 'Prioritized list of MITRE ATT&CK techniques with the weakest detection coverage (detection debt)' — a specific verb+resource+outcome. It distinguishes from siblings like get_mitre_coverage (which likely shows full coverage) and get_mitre_technique (likely deep dives on one technique) by explicitly framing the output as a prioritized debt list for targeting detection work.

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 implies the use case: 'so you can target where to build detections next,' which gives clear context for when to invoke it. It doesn't explicitly name alternatives or exclusions (when-not-to-use), but among the MITRE siblings the purpose is distinct enough that the context is largely self-evident.

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