broadcast_mission_state

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

With no annotations, the description carries the full burden. 'Broadcast ... to all subscribed MCP clients' does disclose the fan-out side effect, which is the one genuinely useful behavioral hint, but there is nothing about permissions, delivery guarantees, failure behavior when no clients are subscribed, or idempotency.

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?

One tight, front-loaded sentence with no filler. It is well-structured, though the brevity here reflects under-specification rather than deliberate economy.

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 explained. However, for a side-effecting broadcast with a free-form mission_data payload and no annotations, the description omits the payload contract and the runtime behavior an agent needs to invoke it correctly.

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 0% for two parameters, one of which (mission_data) is an open-ended nested object with additionalProperties: true. The description adds no meaning for either mission_data or priority (including what the integer default of 0 implies), so it fails to compensate for the total coverage 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?

The description names a specific verb (Broadcast), resource (mission state update), and audience (all subscribed MCP clients), which is more than a restatement of the name. It does not, however, differentiate itself from siblings such as subscribe_mission_updates or mission_queue, whose relationship to this fan-out notification is left unstated.

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?

There is no guidance on when to call this rather than the sibling mission/subscription tools, nor any precondition (e.g., that clients must have subscribed first). The agent must infer usage entirely from the tool name.

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