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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It indicates the input-output mapping but does not clarify whether the query should be a technique ID (e.g., T1059), a name, an alias, or what the detection output contains beyond the word 'detection'.

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 very short and information-dense, using an arrow notation to convey the transformation. The 'MITRE Technique:' prefix largely repeats the tool name, but the overall structure is front-loaded and economical.

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?

While the tool is simple and has an output schema, the description does not define the input format or the structure of 'tactics + detection.' With zero annotations and zero parameter documentation, an agent has to guess how to supply q and what to expect in return.

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 input schema has a single 'q' parameter with no description, and schema coverage is 0%. The phrase 'ATT&CK technique' implies q is a technique, but it does not specify the expected format, accepted values, or whether it is a search term or exact identifier.

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 states a clear mapping: an ATT&CK technique is transformed into tactics and detection. It names the exact resource domain and the kind of output, even though it lacks an explicit verb.

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 about when to use this tool versus related threat-intel tools (e.g., apt_track, threat_actor, threat_pattern). There are no exclusions, alternatives, or prerequisite conditions described.

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