mc_connect

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

No annotations provided, but description explains port scanning, reset behavior, and auto-connect. Could detail session info more, but overall transparent.

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?

Efficiently structured with primary purpose first, then optional uses, then parameter-specific guidance. No extraneous words.

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?

Adequately covers connection behavior for a simple tool with full schema coverage. Missing detail on what 'session info' entails, but reasonable given no output schema.

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?

Adds meaning beyond schema by explaining port scanning range and reset usage. Schema descriptions are already good, and description reinforces them with examples.

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?

Clearly states 'Connect to a running Minecraft instance with the DebugBridge mod.' and differentiates from siblings like mc_quit_client and mc_leave_server.

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?

Provides context on when to use manually (non-default port, reconnect, get session info) and mentions auto-connect behavior. Lacks explicit when-not to use but is sufficiently informative.

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