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

With no annotations, the description carries the burden itself, and it does disclose the return payload (mitre_id, name, description, tactic(s), threat actors, malware) and implies a read-only single-record fetch. It stops short of stating not-found/error behavior or authentication requirements, which is the remaining gap for a zero-annotation 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?

Three tight sentences: what it fetches and returns, then the disambiguation rule, then the escape hatch to the general query tool. Front-loaded with the primary action and no filler.

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?

There is no output schema, so listing the returned fields is genuinely necessary and present, and the identifier formats are covered. The only shortfall is unstated behavior when the identifier matches nothing or is ambiguous, which matters for a lookup by free-form name.

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 100% and the schema already defines identifier as a MITRE ATT&CK ID, UUID, or technique name with the T1566 example. The description restates exactly that, adding no format precedence or fallback behavior beyond the schema. Baseline 3 applies.

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?

Starts with a specific verb and resource ("Fetch a single Mallory attack pattern by identifier") and enumerates the accepted identifier forms plus the returned fields. It is clearly distinguishable from listAttackPatterns (enumeration) and queryApi (pivots/advanced queries) by name.

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?

Explicitly routes the agent: if you only have a name or search terms, call listAttackPatterns first; for relationship pivots or cross-entity queries, use queryApi. Both the when-to-use and the when-not-to-use conditions are stated with the named alternative.

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