ping

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

With no annotations, the description bears full disclosure burden; it conveys that this is a non-mutating liveness check by implication, but never states side-effect-free behavior, cost/latency, or what a failure looks like. Because an output schema exists, omission of return details is acceptable, keeping this at a minimum-viable 3.

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 with no filler, exactly proportionate to a trivial liveness probe. Every word earns its place.

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 already defining the response, the description covers what an agent needs to select and invoke it. A brief note on typical placement (pre-flight vs. troubleshooting) would close the only remaining 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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description adds no misleading parameter hints, which is the correct behavior here.

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?

States a specific verb ('check') and resource ('the market-research server is running'), making the health-check nature unambiguous. It does not explicitly differentiate itself from the ten data-retrieval siblings, but the distinction is obvious from the verb and the zero-parameter schema.

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?

Usage is only implied: an agent can infer this is a connectivity/liveness probe, but the description never says when to call it (e.g., before a batch of data calls, or after a suspected outage) or that it should not be used to validate data availability. No alternatives or exclusions are named.

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