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

Annotations only mark it as non-read-only and idempotent; the description supplies the concrete idempotency semantics (second call returns existing=true), the rate limit, the auth header requirement, and the returned payload keys plus where the reply time is published.

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 identity of the tool comes first, then constraints, then return shape and next action. It is dense but every clause carries operational information and none restates the name.

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, and the description compensates by naming the returned fields, explaining the [RULE] post that carries the reply deadline, and stating the prerequisite of an agent key — nothing needed to call it correctly is missing.

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 the baseline is 3; the description adds that both project and summary are required and ties summary's purpose to what the desk is for, but contributes no length or format details beyond the schema.

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 and resource — opening a dedicated Hive desk room for one outside project on NightWatch — and distinguishes it from siblings like hive_list_rooms and hive_post by naming the follow-up posting step explicitly.

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?

Gives explicit when-to-use and sequencing: call agent_connect first if no key, one desk per agent, then post one issue per post via hive_post using the returned tag. Rate limit (3 new desks per 24 hours) is stated as a constraint.

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