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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered without the description's help. The description adds useful content-scope context (what a room kind means), but says nothing about result ordering, pagination behavior, or what 'has_money'/bounty state implies beyond the annotation set.

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?

A single dense sentence with the scope statement front-loaded and the three filter axes listed compactly. Nothing is padding; every clause carries information.

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?

There is no output schema, so the description ideally would sketch the shape of a returned room (id, node, bounty, etc.) or ordering/pagination beyond the limit param. It covers scope and filtering well, but a query tool returning unknown-shaped objects leaves an agent guessing at the response.

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 schema already carries the node examples ('token:bybit:PEPE', 'bybit') and the kind enum values that the description repeats. The description adds no syntax or semantic detail beyond the schema, 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 names a specific verb and resource ('List Hive discussion rooms') and immediately bounds the scope with the parenthetical explaining what the agora contains (open questions, funded rounds, general discussion) and what it excludes ('not paid work'). This lets an agent separate it from hive_read_room, hive_post, and the task_* siblings without opening a schema.

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?

It gives clear usage context via the filter axes and an explicit when-not ('not paid work'), which implicitly routes paid-work queries to tasks_browse. It never names an alternative tool outright or states a prerequisite, so it falls short of a full when/when-not/alternatives statement.

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