MCP Basics

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. It doesn't indicate whether this is a read-only or destructive operation, what permissions might be needed, whether it modifies files, what side effects to expect, or any rate limits. The description simply states how to execute it without explaining what happens during execution. This leaves the agent with no understanding of the tool's behavior.

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 extremely concise ('Execute mcp-translator: npx ts-migrate') but this brevity comes at the cost of being under-specified rather than efficiently informative. While it's front-loaded with the execution command, it lacks any explanatory content that would help an agent understand the tool's purpose or usage. The single sentence doesn't waste words but also doesn't provide meaningful information.

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 that this is a tool with no annotations, no output schema, and a description that provides minimal information, the description is completely inadequate. For a tool that likely performs code migration operations (inferred from 'ts-migrate'), the description should explain what the tool does, when to use it, what behavior to expect, and what results it produces. The current description fails to provide the contextual information needed for an agent to use this tool effectively.

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 description provides no parameter information whatsoever. However, with 100% schema description coverage for the single parameter 'directory', the schema already fully documents that this is an optional directory parameter. Since the description adds zero value beyond what's in the schema, the baseline score of 3 is appropriate. The description doesn't compensate but doesn't need to given complete schema coverage.

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 'Execute mcp-translator: npx ts-migrate' is essentially a tautology that restates the tool name with a command prefix. It doesn't explain what the tool actually does (e.g., migrating TypeScript code, transforming JavaScript to TypeScript, or performing specific code migrations). While it mentions 'npx ts-migrate', this is just the execution method rather than the purpose. The description fails to distinguish this tool from its siblings like mcp-formatter or mcp-linter.

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 no guidance on when to use this tool versus alternatives. There's no mention of appropriate contexts (e.g., when migrating TypeScript projects, during codebase upgrades), prerequisites, or when not to use it. It doesn't reference sibling tools like mcp-formatter or mcp-linter that might serve different purposes. The user is left with no information about when this tool is the right choice.

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