ping

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

With no annotations available, the description carries the behavioral burden. It transparently discloses that the tool is non-mutating (a probe) and that it returns engine status, version, and memory metrics while verifying the communication path. It could add explicit 'no side effects' phrasing, but the intent is clear.

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 two concise sentences with no filler. The core purpose—probe and returned metrics—is front-loaded, and the supporting sentence explains why the tool exists, making every word purposeful.

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 ping tool, the description covers what it does, what it returns, and its verification role. The optional session_id parameter is not explained, but the presence of an output schema and the lightweight nature reduce the need for deeper detail.

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 schema has zero description coverage for the session_id parameter, and the description does not directly explain session_id. The phrase 'active Godot Editor session' hints at the parameter's context but does not clarify values, defaults, or behavior, so the description adds only minimal semantic value.

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 identifies the tool as a lightweight readiness probe that echoes engine status, version, and memory metrics, and it states the end-to-end verification purpose. This specific verb+resource framing distinguishes it from heavier management siblings like editor_state, logs_read, or session_manage.

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 description implies when to use the tool: as a lightweight readiness check before relying on the MCP connection to the Godot Editor. However, it does not explicitly state when not to use it or name alternatives, leaving some inference required.

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