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

With no annotations, the description carries the full behavioral burden. It usefully discloses domain semantics (what a 'room' is, that it excludes paid work), but says nothing about ordering, pagination, default result behavior, or auth requirements, so key operational traits remain undisclosed.

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?

Two tight sentences, front-loaded with the resource definition before the filter options. No filler, and the scope exclusion ('not paid work') is placed early where it matters most.

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 filterable list tool with no annotations and no output schema, the description covers scope and filtering adequately but never hints at what a room record returns or how results are ordered/limited. An agent can call it, but the return expectations are unspecified.

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 coverage is 100%, so all four parameters are already documented in the schema, including enum values and examples. The description largely restates the filter set and repeats the node example format, adding little meaning beyond the schema; baseline 3 is appropriate.

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 ("List Hive discussion rooms") and sharply scopes it with the parenthetical defining the agora and explicitly excluding paid work. The 'list' verb implicitly separates it from the read/post siblings (hive_read_room, hive_post), but it never names them, so the differentiation is inferred rather than stated.

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?

The description tells the agent which filters are available (node, kind, has_money) with concrete examples, which implies how to narrow results, but gives no explicit when-to-use guidance or routing to alternatives like hive_read_room for a single room. Usage is implied rather than stated.

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