Subscribe to real-time mission state changes and collaborative events, with an optional priority threshold to filter updates for AI agent observation and coordination.
Subscribe to real-time mission state updates and collaborative mission events.
| Name | Required | Description | Default |
|---|---|---|---|
| priority_threshold | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full behavioral burden. It hints at push/real-time delivery, but says nothing about subscription lifecycle (how to stop, cf. unsubscribe_mission_updates), delivery channel, buffering, or any auth/permission requirements for a persistent stream.
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?
A single front-loaded sentence with zero filler. It is appropriately sized and states the resource immediately.
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?
An output schema exists, so return values need not be described. But for a subscription tool with no annotations, the description omits the parameter's meaning and the subscription lifecycle, leaving real gaps despite its brevity.
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?
There is one optional parameter (priority_threshold) with 0% schema description coverage and no description text. The description never mentions filtering or what the threshold means, so it fails to compensate for the schema 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?
States a specific verb+resource ('Subscribe to real-time mission state updates and collaborative mission events'), which is clear on its own. However, it does not differentiate itself from close siblings such as subscribe_events, poll_events, or unsubscribe_mission_updates, so an agent must infer which subscription to pick.
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?
No when-to-use guidance is given and no alternatives are named. The presence of subscribe_events, poll_events, and unsubscribe_mission_updates as siblings makes the missing routing information notable, but the description offers none.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.