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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the concrete behavioral fact that the tool returns 'pong', which the agent can expect and check. This goes beyond what annotations provide, justifying a score above baseline.

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?

A single, front-loaded sentence containing only essential information: purpose, return value, and use case. No padding, no redundancy. Every word contributes to an agent's ability to understand and invoke the tool.

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 no-input, trivial-behavior tool with an output schema and safety annotations already present, the description provides everything needed to call it correctly. The agent knows what the tool doeshare and what to expect in response, leaving no critical gaps.

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 schema description coverage is 100% vacuously. There is nothing for the description to clarify about parameters. According to the baseline, 0 params earns a 4, and the description appropriately says nothing about inputs.

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 states a specific purpose: a health check that returns pong to verify MCP connectivity. It distinguishes the tool from all stock-analysis siblings, which serve entirely different functions. The resource ('MCP connectivity') and expected behavior ('returns pong') are clearly named.

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 clearly implies when to use the tool: whenever an agent needs to confirm MCP connectivity. It does not explicitly mention alternatives or exclusions, but the purpose is so distinct from sibling tools that no ambiguity exists. This meets the 'clear context' level, though not the 'explicit when-not/alternatives' bar.

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