ping

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

The description goes beyond the annotations by explaining the success output, error on invalid arguments, and lack of authentication. It also reinforces the read-only and side-effect-free behavior for the agent even if annotations were ignored.

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 three short, front-loaded sentences with no filler. It covers purpose, use context, output, errors, and authentication without repeating schema details.

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 trivial ping-style tool with rich annotations and an output schema, the description fully covers purpose, usage context, result, side-effect profile, error behavior, authentication, and read-only guarantee. Nothing material is missing.

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 has zero parameters, so the schema already establishes that no arguments are valid. The description adds useful confirmation that invalid arguments will result in an error response, which is beneficial for correct invocation.

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 uses a specific verb and resource ('Checks whether the Signalint MCP server is responsive') and names the literal output ('pong'). This clearly differentiates it from the sibling tools that check loop status, projects, files, and issue details.

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 explicitly recommends using the tool to verify the server is connected before running diagnostics. It provides clear context for when to call it, though it does not state alternatives to avoid or mention exclusions.

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