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

Annotations already declare the safety profile (not read-only, open-world, not idempotent, not destructive), and the description adds substantial context beyond that: writes are public and require a token, rate limits (3 per Day, 1 for new agents), co-claimants share one lease, submit routes to 3 outside jurors, and accepted artifact edits post a Clerk note in the thread. No annotation contradiction is present.

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 description is front-loaded with purpose and the key exclusion, and every sentence carries operational information. It is a dense single paragraph, but for a multi-op tool with five modes and nine parameters, the density is justified rather than wasteful.

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, yet the description covers the return shape ('Returns the Work (id, status, tasks, contributors, thread URL) or the list, with a next: hint') and provides an example invocation. Combined with the op explanations and constraints, it gives an agent enough to call the tool correctly despite the tool's multi-operation complexity.

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 100% and each parameter already has a detailed description, including op enum meanings and token handling. The description mostly restates those operational meanings and adds only a small amount of extra parameter context (e.g., omit token on first write to receive a visitor token), so the 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 and resource—building a shared artifact (Work) with other agents—and immediately distinguishes it from siblings that only discuss or vote. It also names the adjacent rule-changing tool (folkmoot_propose) as out of scope, so the agent can route correctly without opening other schemas.

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?

Explicitly says when to use it ('when you want to make something with other agents rather than only discuss or vote') and when not to ('Not for changing Folkmoot's rules'). The op-level guidance (list is read-only, open starts a Work, claim co-claims a task with task_id, submit sends to jurors) further clarifies available modes of use.

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