AI Team OS

Overview Schema Source Related Servers Discussions Admin

briefing_add

Park decisions that arise when the user is away, so autonomous loops, background workflows, or sub-agent reports can continue and await the user's answer.

Instructions

Park a decision for the user while the user is NOT in the conversation.

Only for questions that come up when nobody can answer them now: autonomous /loop work, background workflows, another session's findings, or a sub-agent's report that leaves something "for the user to decide". If the user is in the conversation, ask them directly instead; the result carries user_present and a hint when this project saw a user message in the last 15 minutes. When the user later answers an item, call briefing_resolve on that item right away. Pending items expire after 14 days without an answer (status only, never deleted).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tags`	No	Free-form topic tags for filtering the queue (e.g. ["release"])
`title`	Yes	Brief description of the decision needed
`options`	No	Available choices (e.g. "A: option1 / B: option2")
`urgency`	No	high / medium / low	medium
`description`	No	Detailed context
`recommendation`	No	Leader's suggested choice and reasoning

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.11.2Aug 3, 2026

addedInput schema / properties / tags

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Free-form topic tags for filtering the queue (e.g. [\"release\"])"
+}

First observedv1.9.0Jul 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the user_present/hint return signals and their 15-minute lookback window, the 14-day expiry of unanswered items, and that expiry affects status only (never deletion). These are non-obvious lifecycle and side-effect facts an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The routing rule is front-loaded and every sentence adds a distinct rule (when to use, exclusion, resolve path, expiry). Slightly dense, but no sentence is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still supplies the lifecycle and return-signal context an agent needs to route and later resolve items. Nothing required to call or follow up on this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% across all 6 parameters, so the schema already documents title, options, urgency, tags, description and recommendation. The description adds no format or constraint detail beyond that, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (park a decision for the user) plus the critical scope condition (only when the user is NOT in the conversation). An agent can distinguish it from briefing_resolve and briefing_list without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly enumerates the situations that qualify (autonomous /loop work, background workflows, another session's findings, sub-agent reports) and the exclusion (if the user is present, ask directly instead). It also names the follow-up tool, briefing_resolve, and the condition that triggers it.

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

Deploy Server