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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description goes beyond them with the upstream source URL, the 15-minute regeneration cadence, and a security warning that returned tag values are community-authored and must be treated as data, not instructions. It stops short of describing pagination or result ordering, but for a read-only tool this is solid added context.

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 sentences with the purpose front-loaded, followed by usage examples, provenance, and a safety note; every sentence carries information. It is slightly dense but not padded.

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?

No output schema exists, yet the description names what is returned (top tags plus IOC-type distribution), where it comes from, how fresh it is, and how to treat the payload. Combined with annotations and full schema coverage, an agent has everything needed to call it safely and correctly.

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 window enum values are fully documented in the schema itself, so the description need not restate them. It adds no syntax or interpretation detail beyond the schema, making the baseline 3 correct.

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+resource ('Top tags and IOC-type distribution for a given time window') and adds the data provenance (counts.json aggregate). It does not, however, differentiate itself from the closely-named sibling get_trends, leaving the agent to guess which trending tool to pick.

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?

Offers example user intents ('what is the infosec community talking about right now', 'which malware family is spiking this week'), which implies when the tool is appropriate. It gives no explicit when-not conditions and never names get_trends or get_tag_info as alternatives, so routing between the three trending/tag tools is left to inference.

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