threatfoxTag

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds that ABUSECH_AUTH_KEY is required, a real behavioral constraint, but says nothing about rate limits, result caps behavior, or return shape.

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?

Two short clauses, front-loaded with the action and resource, and the auth requirement appended without padding. Slightly terse but no wasted sentences.

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 low-complexity read-only search with full schema coverage, the essentials are present, but with no output schema the description should say something about what comes back (IOC records, fields, volume). The missing return-shape context is the main gap.

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%, so both parameters (tag and limit, including its 1-1000 range and default) are already fully documented in the schema. The description only restates the tag concept with examples, adding nothing beyond what the schema provides — baseline 3.

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 (search) and resource (ThreatFox IOCs) with the scoping key (tag), which is enough to distinguish it from sibling tools like threatfoxSearch or threatfoxGetIocs. It does not name those siblings explicitly, so it stops short of a 5.

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 gives no when-to-use context and no alternatives — it never explains how this differs from threatfoxSearch, threatfoxMalware, or threatfoxGetIocs, all of which are plausible lookups in the same family. The only guidance is an auth prerequisite, which is not usage routing.

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