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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Track APT campaigns' without explaining query semantics, data freshness, scope limits, required context, or what constitutes a campaign lookup. The output schema covers return structure but not behavioral traits.

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 short and front-loaded, but it partially repeats the title 'APT Track' and contains no additional structured guidance. It is efficient, but the brevity comes at the cost of useful detail.

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?

Although the tool is low-complexity with one optional parameter and an output schema, the description still leaves the agent unable to determine what to pass in 'q' or when this tool is preferable to nearby threat-intel siblings. It is minimally viable but not complete enough for confident 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?

Schema description coverage is 0%, and the description does not explain what 'q' means or how it should be formatted. The only hint is the word 'Track', which suggests q may be a search term, but that is left to inference. For a low-coverage schema, the description needed to compensate and did not.

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 specific verb ('Track') and a clear resource ('APT campaigns'), and distinguishes itself from broader sibling tools like threat_actor or mitre_technique by naming its data sources (MITRE + researchers). It is not a tautology, though it is somewhat terse.

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 on when to use this tool versus closely related siblings such as threat_actor, threat_pattern, malware_family, or c2_infrastructure. The description implies a use case but never states an explicit condition or alternative.

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