skill_mcp_start

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

With no annotations, the description bears full responsibility for behavioral disclosure, yet it only states 'Start MCP server for a skill' with no details on side effects, prerequisites, blocking behavior, error cases, or what happens after starting. This is essentially a restatement of the tool's name.

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, front-loaded sentence with no waste. It is appropriately concise for a simple one-parameter tool, though it could have included more behavioral context without becoming verbose.

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 absence of annotations, output schema, and the minimal description, the tool lacks essential context such as success/failure behavior, prerequisites (e.g., skill must be activated), and how to verify the server started. For a start operation with no supporting structure, this is an incomplete description.

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 coverage is 100% with one parameter skill_id described as 'Skill ID with MCP configuration'. The tool description adds minimal context beyond the schema, merely reinforcing that the skill must have MCP configuration. This meets the baseline but does not enhance parameter understanding.

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 uses a specific verb 'Start' with a clear resource 'MCP server for a skill', conveying the tool's core function. However, it does not distinguish itself from related tools like skill_activate or mcp_servers_start, though the 'for a skill' qualifier provides some differentiation.

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 guidance is provided on when to use this tool versus alternatives such as skill_activate, skill_execute, or mcp_servers_start. The description implies usage for starting a skill's MCP server but does not state prerequisites, exclusions, or alternative scenarios.

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