ping_unreal

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

No annotations are present, so the description carries the burden of disclosing behavior. It indicates the tool is a diagnostic ping returning a health response, which implicitly conveys a read-only, non-destructive operation; however, it does not explicitly state side-effect guarantees, failure semantics, or connection details.

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 compact: one primary sentence, an example, and a KB pointer. The main purpose is front-loaded, and there is no filler or redundant restatement.

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 zero-parameter health check with an output schema and an example call, the definition is nearly complete. It lacks an explicit statement about side effects or failure behavior, but 'ping' and 'health response' largely cover that gap.

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 tool takes zero parameters, so the input schema fully exhausts parameter meaning. There is nothing for the description to add about parameters, making the baseline-4 score appropriate.

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 opens with a specific action, 'Ping the UnrealMCP bridge,' and a concrete result, 'return its health response,' so an agent knows exactly what the tool does. It does not explicitly distinguish itself from sibling health/ping tools such as ghostrigger_ping or server_lifecycle_status, but the resource is unique enough to avoid serious confusion.

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?

There is no when-to-use guidance: no mention of using this to verify bridge availability before other calls, no exclusions, and no alternatives. The example only demonstrates invocation, and the KB pointer is a reference link rather than actionable usage context.

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