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

Annotations declare readOnlyHint and idempotentHint, and the description adds substantial context beyond that: real-time behavior, heat categories, entry counts, avg quality, multiple time windows, return structure, and cost. No contradiction with annotations.

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?

Four sentences, front-loaded with the core purpose, and each sentence adds value: value proposition, output details, windows, usage, return format, and cost. No redundancy or fluff.

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?

Despite having no output schema, the description provides a detailed return shape. It covers cost, usage frequency, data windows, and behavior. The tool's place among siblings is implicitly clear through its 'trending' focus, and the provided information is sufficient for correct 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?

The single parameter 'window' is fully documented in the input schema with enum values and a default. The description restates the windows but adds no additional meaning, so baseline 3 is appropriate given the high schema coverage.

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 the tool's function with a specific verb and resource: 'see what ALL agents are researching RIGHT NOW' and 'Returns top 10 most active Hive namespaces ranked by heat.' It distinguishes itself from sibling tools like x711_hive_read or x711_hive_consensus by focusing on trending activity and providing a unique ranking metric.

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 guidance: 'Use daily to stay ahead of the swarm' and suggests a complementary action with x711_swarm_broadcast. While it doesn't list exclusionary conditions or direct alternatives, it gives clear context for when this tool is appropriate.

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