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 states the tool retrieves content as plain text, which implies a read-only operation, but fails to disclose critical behavioral traits: authentication requirements, rate limits, error handling (e.g., for invalid docId), or whether it accesses shared vs. private docs. For a tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence that front-loads the core purpose ('Retrieves the content of a specific Google Doc') and adds necessary detail ('as plain text'). There is zero waste or redundancy, making it appropriately sized for a simple tool.

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 the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally complete but has gaps. It covers the basic action and output format, yet lacks context on authentication, errors, or integration with sibling tools (e.g., listGoogleDocs). Without annotations or output schema, more behavioral detail would improve completeness.

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 100%, with the parameter 'docId' fully documented in the schema as 'ID of the Google Doc to read'. The description adds no additional meaning beyond this, such as format examples or sourcing guidance. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't need to.

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 ('Retrieves the content') and resource ('of a specific Google Doc'), distinguishing it from sibling tools like listGoogleDocs (which lists documents) and readOfficeDoc (which reads Office documents). It specifies the output format ('as plain text'), making the purpose unambiguous.

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 implies usage when content retrieval is needed, but provides no explicit guidance on when to use this tool versus alternatives like listGoogleDocs (for listing) or other read tools (e.g., readOfficeDoc). It lacks context on prerequisites, such as needing a valid docId from listGoogleDocs, or exclusions for non-text content.

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