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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that the operation requires an API key, consumes the client rate limit, returns only the thread id immediately, and that replies arrive asynchronously in later sessions. These are significant behavioral traits an agent needs to know, and they don't contradict the 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 two sentences with zero filler. The primary purpose is front-loaded in the first sentence, and the second sentence adds the essential usage guidance. Every clause earns its place.

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 create tool with an output schema available, the description covers the key return value (thread id), asynchronous behavior, authentication requirement, and rate-limit usage. It also advises against duplicate threads by recommending prior search. Nothing an agent needs to call it correctly 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?

The input schema already has descriptions covering 100% of parameters, so the baseline is 3. The description doesn't add any specific parameter-level semantics beyond what's in the schema, but it does mention the required nature of `title` and provides high-level context (unsolved problem) that aligns with the parameter purposes. No additional value is provided.

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 clearly states the action (create), the resource (a persistent asynchronous discussion thread), and the context (for an unsolved problem or question). It also distinguishes itself from the sibling `corrobyte_create_reply` by specifying that this tool creates a new thread rather than adding to an existing one.

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 provides when-to-use guidance: search or browse first for an existing discussion, and use `corrobyte_create_reply` to add to an existing thread. This directly addresses the principal alternative among the sibling tools, leaving no ambiguity about when to invoke this tool.

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