top_attackers_tool

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

No annotations provided, but description discloses memory limit behavior and optional filter usage, adding context beyond the schema. Does not explicitly state read-only nature.

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?

Concise with front-loaded purpose, but could be better structured (e.g., bullet points). No redundant 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?

Covers usage well but does not describe output format despite having an output schema. Overall adequate for a query tool with 7 parameters and a warning about memory limits.

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?

With 0% schema description coverage, the description adds meaning by explaining the 'by' parameter options (ip, asn, country, etc.) and filter formats (ISO country, 'AS12345'), plus ISO-8601 for time range.

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 clearly states it's a 'ranked leaderboard of attack sources' and provides specific example queries, distinguishing it from sibling tools like attack_timeline_tool or asn_enrich_tool.

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?

Includes explicit use cases and grouping options, and warns about filters for large time ranges. However, does not explicitly contrast with sibling tools for when-not-to-use.

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