WayStation MCP Server

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 draft can be edited and sent later, and optionally created as a reply, which adds useful behavioral context. However, it lacks details on permissions, rate limits, error handling, or what happens if parameters are invalid, leaving gaps for a mutation tool.

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 description is front-loaded with the core purpose in the first sentence and adds an optional feature in the second, with no wasted words. It is appropriately sized and structured for clarity.

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?

Given no annotations and no output schema, the description is moderately complete but has gaps. It covers the basic purpose and some behavioral traits, but for a mutation tool with 7 parameters, it lacks details on return values, error cases, or advanced usage scenarios, making it adequate but not fully comprehensive.

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?

The input schema has 100% description coverage, so the baseline is 3. The description does not add any parameter-specific semantics beyond what the schema provides (e.g., it doesn't clarify format for 'threadId' or 'inReplyTo' beyond the schema's descriptions), so it meets but does not exceed the baseline.

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 specific action ('creates and saves a draft email') and resource ('in the user's Gmail account'), with additional context about editing and sending later. It distinguishes from the sibling tool 'sendGmailEmail' by specifying this is for drafts, not immediate sending.

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 provides clear usage context by indicating the tool is for creating drafts that can be edited later and optionally as replies. However, it does not explicitly state when to use this versus alternatives like 'sendGmailEmail' or other email-related tools, though the distinction is implied by the focus on drafts.

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