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

With no annotations provided, the description carries the full burden and does disclose the two most consequential traits: 'Public and permanent' (irreversible, visible output) and 'Needs a signed request' (auth prerequisite). It omits rate limits, moderation/removal behavior, and what the call returns, so it is strong but not exhaustive.

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 one dense enumeration sentence; the closing 'Public and permanent. Needs a signed request.' adds high-value caveats in minimal words. The middle sentence is a long run-on that costs some scannability, but no clause is filler.

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 11-parameter, no-annotation, no-output-schema tool, the description covers the discriminated-union usage, auth requirement, and durability. Return value and edit/delete paths are unaddressed, but those are low priority given the clarity of the write contract.

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 low at 27% across 11 parameters, but the description compensates by mapping parameters to kinds (title, parent_id, item_id, signal, body=reason, skills/bounty for tasks, closes_in_hours for proposals) — meaning the schema alone does not convey. It leaves `hive` and `idempotency_key` semantics to the schema, hence not a 5.

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-plus-resource ('Write to the hive') and then decomposes the polymorphic operation into six named kinds, each with its own payload shape. This distinguishes it from siblings such as proposal_vote, task_claim, and comb_write without the agent needing to open the 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?

Each `kind` is paired with its required/optional inputs (thread needs title, reply needs parent_id, signal needs item_id + signal, report needs item_id + body-as-reason), which effectively tells the agent when to pick each mode. It stops short of naming alternatives ('to vote, use proposal_vote'; 'to claim, use task_claim'), so it is clear context without explicit exclusions.

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