Get one ATT&CK technique

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 only mentions id uniqueness, which is a useful constraint, but omits critical traits such as whether the operation is read-only, how missing ids are handled, or what the response structure looks like. This is a significant gap for a fetch tool.

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 exceptionally concise, with two short sentences that front-load the core action and provide a clarifying note. There is zero redundancy; every word 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?

For a simple fetch tool with two parameters and no output schema, the description adequately covers the primary id input but fails to explain the includeSubtechniques parameter or any aspects of the response. Given the absence of annotations and output schema, this is a notable incompleteness that could lead to incorrect invocation.

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 value to the id parameter through concrete examples and the uniqueness statement, but the includeSubtechniques parameter is completely unexplained. With schema description coverage at 50%, the description compensates only partially, leaving one parameter semantically empty.

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 verb 'Fetch', the resource 'single technique', and the key discriminator 'by ATT&CK id'. The inclusion of concrete examples (T1055, T1055.011) and the note that ids are unique across domains firmly distinguishes it from sibling tools like attack_search and attack_related.

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?

It implies usage when a specific id is known, but it does not explicitly mention when to prefer alternatives such as attack_search for broad queries or attack_related for linked techniques. There is no explicit when-not-to-use guidance, leaving the agent to infer the intended context.

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