get_mitre_attack_context

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses the return format (dictionary with techniques, tactics, mitigations, detections) but does not mention potential side effects, rate limits, or whether parameters combine with AND/OR semantics. It also doesn't address the behavior when no parameters are provided, leaving ambiguity.

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 with a brief overview followed by Args and Returns sections. It is front-loaded with the purpose, and every sentence adds value (examples, return keys). No fluff or repetition of schema information.

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 output schema exists and the description details the return keys, it misses critical context about parameter interactions and optionality. All parameters are optional, yet the description doesn't state whether at least one must be provided or how multiple filters combine (e.g., AND vs OR). This gap affects usability for an agent deciding how to invoke the tool.

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, and it does well. It gives clear, useful descriptions for each parameter, including concrete examples for technique_id and tactic, and explains search_term as free-text search. It doesn't, however, clarify rules for combining multiple parameters or whether at least one is required.

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 with a specific verb and resource: 'Get context and information about MITRE ATT&CK techniques and tactics.' It distinguishes itself from sibling tools by focusing specifically on MITRE ATT&CK knowledge, unlike security tools like check_ioc_reputation or enrich_ip_with_threat_intel.

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 clear context for when to use the tool ('to help analysts understand and categorize security findings'), making it appropriate for threat analysis and classification. However, it does not explicitly mention when not to use it or provide alternatives among sibling tools, so it stops short of a 5.

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