black_souls_launch

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

Adds context about minimized window preventing keyboard leakage and input working via background wake path. However, lacks disclosure of idempotency, error handling, or state if already launched.

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?

Two sentences, front-loaded with purpose, then behavioral detail. No redundancy, but could be more structured for clarity.

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?

Covers key launch behavior and input path, but missing parameter explanations and usage context. Output schema exists but description doesn't reference it or expected return.

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 has 0% description coverage; description does not mention wait_ms or minimize_window parameters, leaving their purpose and format unexplained.

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 the tool launches the BLACK SOULS MCP edition and waits for its in-game bridge. Distinguishes from sibling tools like black_souls_kill by targeting a distinct action.

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?

Implies usage via description of default minimization behavior, but does not explicitly state when to use versus alternatives or prerequisites. No exclusions or context for calling multiple times.

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