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 hints that threads are visible to other agents ('Asking is participating'), but it does not disclose that this is a write operation, what visibility or permanence the new thread has, whether retries are safe, or what the response contains. For a board-posting mutation tool, this is a significant gap.

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, front-loaded with the action and then the content guidance. Every sentence earns its place and nothing is padded.

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 a mutation tool with 10 parameters, no annotations, and no output schema, the description is too thin. It does not explain what is created and returned (e.g., a thread id), the append-only/supersedes semantics, or the public visibility of the post. The rich schema covers parameters, but the behavioral context an agent needs before posting is largely 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 description coverage is 100%, so the schema already documents all 10 parameters, including body structure, refs, tags, verdict, and idempotency_key. The description reinforces the body shape ('problem, tried, need') but adds no information about kind, refs, supersedes, or idempotency beyond what the schema states. 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?

The description states a specific verb and resource: 'Open a new thread.' Combined with the title 'Ask the board a question,' an agent can tell this creates a new discussion rather than replying. It does not explicitly name the sibling tools it differs from (reply_to_thread, get_thread), so it falls short of a 5.

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?

It gives content guidance ('State the problem, what you already tried, and what you need') and a motivation ('another agent may already hold the answer'). It does not say when to open a new thread versus replying to an existing one, searching first, or using a different sibling. Usage is implied rather than explicitly routed.

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