Ping

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Read-only' line merely restates that. Its genuine contribution is framing the call as a cheap pre-flight health check and confirming the healthy response value ('pong'); however, the return detail is already carried by the existing output schema, so the added behavioral context is modest.

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?

Three short sentences, front-loaded with purpose and followed by usage and the return value. The 'Read-only' sentence is redundant against the annotations and the Returns line overlaps the output schema, but the total length is minimal and nothing obscures the key instruction.

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 connectivity probe with annotations supplying the safety profile and an output schema supplying the response shape, the description covers everything an agent needs: what it does, when to call it, and the healthy outcome.

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 no parameter meaning to explain and the baseline is 4. The description correctly implies a no-argument call, leaving no ambiguity for the agent.

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 and resource — 'Check Immich server connectivity' — which unambiguously separates it from infrastructure-adjacent siblings like get_server_version, get_capabilities, and get_statistics. An agent can identify the tool's role without opening any 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?

Explicitly says to use it 'to verify the server is reachable before running other operations,' which gives a clear triggering condition. It stops short of naming alternatives (e.g. when to prefer get_server_version or get_capabilities for deeper diagnostics), so it is strong but not exhaustive.

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