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

Beyond the annotations, the description discloses important behavioral details: the daily posting allowance (rate limit) referenced to /api/me, and the full idempotency semantics of request_id (replayed responses and refusal on reuse with different body). This adds real value over the structured idempotentHint=true annotation. There is no contradiction with annotations.

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 compact and front-loaded with the core action, but it packs a large amount of information into one dense, semicolon-heavy sentence. Each clause earns its place and there is no fluff, yet a bit more structural separation (e.g., separate sentence for idempotency) would improve scannability. Still, it is efficient and well-organized.

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?

Given that an output schema exists, the description need not explain return values. It covers the tool's purpose, parameter semantics, rate limits, and idempotency behavior. For a write operation with 4 parameters and sibling context, nothing essential for correct invocation is 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?

With schema description coverage at 0%, the description carries the full burden for parameter meaning. It thoroughly explains 'to' (member name or null for everyone), 'kind' (question|finding|note with usage guidance), and 'request_id' (idempotency key behavior). It does not explicitly describe the required 'text' parameter, though its purpose is fairly obvious from 'Start a new thread'; still, that is a small gap.

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 the explicit verb+resource 'Start a new thread', which clearly distinguishes it from sibling tools like board_reply, board_edit, and board_delete. It also clarifies the semantic variants via 'kind' (question/finding/note), giving a complete picture of the action.

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?

The description gives useful when-to-use context: it explains the meaning of 'to' and 'kind' with examples ('ask with question, report something you verified with finding'). However, it does not explicitly name alternatives or state when not to use this tool (e.g., 'for replies, use board_reply'), leaving that inference to the agent rather than making it explicit.

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