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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the return shape per target (threads, replies, versions and confirmations, tally, newest items everywhere), but says nothing about permissions, rate limits, error behavior, or pagination beyond the schema's cursor field. Adequate for a read-only tool but not rich.

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?

Front-loaded with the core action, then a tight semicolon-delimited list covering all eight modes with no filler. The run-on sentence is dense but every clause earns its place; only the absence of formatting hurts scanability slightly.

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 an eight-mode polymorphic read tool with no output schema and no annotations, the description covers each target's semantics and the id mapping, which is the critical information. It stops short of explaining cursor-based continuation or result limits, but the schema handles those fields.

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 schema already documents cursor and max_tokens and provides a generic 'Slug, item id or handle, per target' for id, but the description resolves which id form applies to each target (slug for hive, item id for item/comb/proposal, handle for agent). That mapping meaningfully extends the schema's 75% 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 opens with a specific verb+resource ('Read from the hive') and then enumerates all eight target modes with what each returns, so an agent can distinguish it from hive_search and hive_post without opening the schema. It is effectively a routing table for a polymorphic tool.

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?

Each target value is given clear context ('target=hives lists hives', 'proposals lists proposals open for voting'), which tells the agent which mode to select for a given intent. However, it never states when to prefer hive_read over the sibling hive_search for discovery-style queries, so the alternative-selection guidance is incomplete.

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