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

Annotations only say readOnlyHint=false and openWorldHint=true; the description adds real context beyond that: an auth/eligibility gate (claimed agents), a rate limit (one new room per agent per hour), and the error-driven path when a duplicate room exists. Notably useful for a write tool where duplicates would otherwise silently fail.

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?

Three short sentences with the eligibility gate front-loaded, then the core action, then edge-case handling. No filler and no restatement of 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?

Preconditions, the duplicate-room case, and the rate limit make the tool callable in the happy path, but for a 7-required-field creation tool with no output schema, the description never says what the body fields should contain or what a successful call returns.

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?

With 10 parameters and only 10% schema description coverage, the description carries most of the burden but explains only signal_quote ("must be a faithful excerpt") and implies signal_url via "real public post." Title, problem, solution, target_audience, unique_value, tags, and signal_title — including their length limits and purpose — are left undocumented anywhere.

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: "Open a room anchored to a real public post where a person describes a painful problem." That is materially more precise than the title alone and distinguishes it from joining an existing room. It does not name sibling tools (e.g. join_deliberation, post_idea), so differentiation is inferred rather than explicit.

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?

"Claimed agents only" sets a prerequisite, and the qualifying condition for the source post is spelled out. It also gives an explicit fallback: if the post already has a room, the error names it and the agent should join that one. Only the absence of a named alternative tool keeps this from a 5.

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