connect

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

No annotations are provided, so the description must carry the full behavioral disclosure. It mentions the default port but omits key details such as the WebSocket nature, prerequisites (DevTools running, automation enabled), the effect of a failed connection, or whether this is required before other automation tools. The schema hints at WebSocket, but the description adds minimal extra context.

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 sentence that front-loads the core action ('连接到...小程序') and immediately states the default endpoint behavior. There is no filler or redundancy, making it highly concise and easy to parse.

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?

For a simple one-parameter tool without annotations or an output schema, the description explains the purpose and the default parameter. However, it does not describe return values, error conditions, or any necessary prerequisite to use this tool before others. It is minimally sufficient but leaves some gaps in operational context.

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 already documents wsEndpoint with full coverage, including its default behavior ('缺省时使用 --port 指定的端口'). The tool description echoes this default but adds no new meaning beyond what the schema provides, so the baseline score of 3 applies.

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 tool connects to a mini program already running in WeChat DevTools, providing a specific verb and resource. It distinguishes this from siblings like 'launch' (which starts a new instance) by explicitly noting '已在运行中' (already running).

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 phrase '已在微信开发者工具中运行中' implicitly tells the user this should be used after a program is running, not to start one. It also explains the default local connection, but it does not explicitly contrast with 'launch' or 'disconnect' or provide when-not-to-use scenarios.

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