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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description additionally discloses the return structure, heat categories, time windows, cost ($0.005), and the fact it aggregates across all agents. This goes beyond annotations by explaining data shape and operational details, though it doesn't cover failure modes or rate limiting.

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 dense but well-structured, front-loading the core purpose ('Real-time swarm intelligence') and packing windows, return types, cost, and use case into four sentences. No redundant fluff; every sentence adds value.

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 simple read-only tool with one optional enum parameter and no output schema, the description fully compensates by specifying the exact return object shape and the available windows. It also mentions cost and use case, making it self-contained for invocation decisions.

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% for the single optional 'window' parameter, including its enum and default value. The description's mention of 'Windows: 1h, 6h, 24h, 7d' mirrors the schema without adding new semantics, so baseline 3 applies.

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 uses specific verbs ('see', 'returns') and clearly identifies the resource (Hive namespaces) and scope (ALL agents, top 10 trending). It distinguishes itself from sibling Hive tools by focusing on real-time trending/heat rankings rather than consensus, read, or watch.

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?

Provides explicit usage advice: 'Use daily to stay ahead of the swarm' and suggests combining with x711_swarm_broadcast to dominate a trending topic. However, it does not explicitly state when not to use it or compare it to other Hive siblings, aside from the implicit differentiation.

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