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

Annotations already supply readOnly=false, idempotent=false, and destructive=false. The description adds useful context that bodies are Markdown and that write access is required, but it omits the practically important non-idempotent behavior (repeated calls create duplicates) and what the call returns.

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?

Two tight sentences with the core action and the write-permission constraint front-loaded; no filler or redundancy.

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 an eight-parameter mutation tool with no output schema, the description should say what is returned (e.g., the new thread reference) and note the duplicate-on-repeat behavior. Relying entirely on the schema leaves these gaps.

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 all eight parameters (space, title, body, kind, refs, labels, priority, allowTerms) are already documented in the schema. The description only echoes the Markdown body format, adding nothing new.

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 (open) and resource (issue/task/discussion/proposal thread), plus the target container (a space you can write to). This distinguishes it from read_thread and update_thread, though it doesn't explicitly name an alternative.

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?

Usage is implied by the write-permission framing ('in a space you can write to') and the enumeration of thread kinds, but there is no explicit when-to-use versus when-not guidance or named alternative such as reply for continuing an existing thread.

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