promote_suggestion

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

No annotations are provided, so the description carries the full burden. It discloses that the tool creates a real thread (mutation), but does not mention what happens to the original suggestion (e.g., is it removed?), any authorization needs, or error conditions. Some behavioral aspects are left unclear.

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 sentences, no wasted words, front-loaded with the key action. Highly concise.

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?

No output schema is present, and the description does not explain what the tool returns or fails. It also omits prerequisites like an active session. While it covers the core behavior, completeness is moderate given the complexity of creating a thread from a suggestion.

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 coverage is 100%, and the parameter descriptions in the schema are already clear. The description's mention of 'suggestion_id from session_start's suggested_threads list' adds little beyond what the schema provides. The baseline of 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 clearly states the action ('promote a suggested thread to an open thread') and specifies the resource (suggestion_id from session_start's suggested_threads list). It distinguishes from sibling tools like create_thread (which creates from scratch) and dismiss_suggestion (which dismisses).

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 context for when to use (when you have a suggestion_id from the suggested_threads list) but does not explicitly state when not to use or contrast with alternatives like create_thread or dismiss_suggestion. The agent could benefit from clearer differentiation.

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