snap_ping

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: the call returns who is authorized and the safety limits the server operates under, which tells the agent what to expect in the response. No rate-limit or failure-mode detail, hence 4 not 5.

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 three coordinated clauses; every clause adds a distinct fact (auth validity, identity, limits). Slightly padded by 'this server is running with', which could be trimmed without loss.

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, read-only, no-output-schema diagnostic tool, the description covers purpose and the shape of the returned information, which is about as much as an agent needs. It lacks only explicit failure semantics (what happens when credentials are invalid), a minor gap at this complexity.

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 no-arg tool is 4. Nothing in the description misleads 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?

Names a specific verb ('Check') and resource ('Snap credentials'), then enumerates the two extra outputs (authorized identity, server safety limits). This reads clearly as a diagnostic/health-check tool. It does not explicitly contrast itself with the similarly-scoped 'snap_connect' sibling, so it stops short of a 5.

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 implied — verify credentials before or while troubleshooting — but there is no explicit 'use this when' clause, no exclusions, and no pointer to an alternative such as snap_connect for establishing credentials. An agent can infer the context but not the routing rule.

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