Ping the Galley MCP kernel

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does state the primary behavior (returns 'pong' with kernel version), but it does not disclose what the 'echo' parameter does, any side effects, or permissions required. This is a partial disclosure.

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 extremely concise—two short sentences with no wasted words. The primary purpose is front-loaded. However, it omits crucial details about the parameter, so the conciseness comes at the expense of completeness.

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 tool with one optional parameter and no annotations, the description is incomplete. It lacks any explanation of the 'echo' parameter, does not describe potential error conditions, and provides no information on return format beyond the string 'pong'. The tool could be called with an unexpected parameter value, and the agent would have no guidance.

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 one optional parameter 'echo' with no description, and the tool description does not mention it at all. With 0% schema description coverage, the description must compensate, but it fails to explain the parameter's purpose or effect. An agent cannot infer what 'echo' does.

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's purpose as a liveness check that returns 'pong' with the kernel version. The title 'Ping the Galley MCP kernel' reinforces the specific action. It is distinct from sibling tools like read_document or propose_edit, which handle file operations.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that it is for connectivity checks or any conditions for invocation. The agent is left to infer usage from the tool name and title.

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