MCP Multi-Agent Coordinate

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not the sole source there. It does add real operational context the annotations lack: cost of 100 credits (Tier 4) and the POST endpoint. It says nothing about latency, how many personas are permitted, or what the synthesis step produces.

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?

The behavioral statement is front-loaded in a single, waste-free sentence, with bracketed metadata after it. The "[Required: question, agents]" line duplicates the schema's required array, which is the only clear filler.

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, this is a complex, credit-consuming tool with a nested chart object and an open-ended agents list, and the description omits the chart parameter's role and any hint about how personas are chosen, leaving meaningful gaps before a paid call.

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 only 25%, so the description carries the burden and mostly fails: it restates the required set (question, agents) which the schema already enforces, and says "N personas" without revealing the 2-4 item bounds or what valid agent identifiers look like. The nested chart object and the language enum receive no mention at all.

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?

"Run N personas in parallel + LLM synthesis" names a mechanism (parallel personas plus a synthesis step) rather than a clear astrology resource, and leaves "personas" undefined. It does not distinguish itself from close siblings such as astroway_mcp_agent_debate or astroway_mcp_ai_chat, so an agent must infer the difference.

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 or when-not-to-use guidance is given; the only selection signal is a credit cost and a group tag. The obvious alternatives (agent_debate, ai_chat, ai_comparison_coach) are never mentioned, so routing depends entirely on the name.

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