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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), and the description adds real context beyond them: what fields come back and the important caveat that an actor can have zero mapped attacks because no ATT&CK technique id was cited, rather than omitted by error. It doesn't discuss result size/pagination, but with zero parameters a full unfiltered listing is implied.

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 purpose, the scope exclusion, and the primary use case are front-loaded in the first three sentences. The final sentence about unmapped attacks is longer than needed and slightly repetitive ('the report documenting it never cited a specific MITRE ATT&CK technique id, so nothing is attributed to it rather than guessed'), but it carries substantive behavioral 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?

For a no-parameter read-only list tool with no output schema, the description is complete: it names the returned fields, states the scope boundary, routes to the correct follow-up tool, and warns about a legitimate empty-result case that would otherwise look like a bug.

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 tool takes no parameters, so there is nothing for the description to disambiguate beyond noting the listing is not scoped to a cloud service. Baseline 4 applies for a zero-parameter tool.

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?

States a specific verb and resource ('List every real-world threat actor Mitigant's catalog tracks'), enumerates the returned fields, and explicitly scopes the tool ('Not scoped to a cloud service'). It is clearly distinguishable from sibling get_attacks_by_threat_actor, which it names.

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?

Gives two concrete when-to-use cases: resolving an actor's exact name before calling get_attacks_by_threat_actor, and summarizing an actor from its description. It also names the alternative tool explicitly and provides example identifiers, leaving nothing to inference.

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