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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and locality profile is covered and the bar is lower. The description only adds the return token 'pong', which is arguably duplicative given an output schema exists; it says nothing about latency, auth requirements, or failure behaviour.

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 short clause, front-loaded with the purpose and containing no filler. Nothing irrelevant is included for a trivial liveness probe.

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?

With no parameters, an output schema supplied, and annotations covering the read-only profile, an agent has everything needed to invoke this tool correctly. The description adds the one thing not obvious from structured data: the expected response token.

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 per the baseline this scores 4. There is nothing for the description to disambiguate in the empty schema.

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?

"Connectivity-Check" names a specific action plus the expected return value ('pong'), so the agent knows exactly what the tool does. It doesn't need to differentiate from siblings because none of the ~250 other tools is a health check, but it also makes no explicit statement of its unique role.

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: the label 'Connectivity-Check' suggests calling it to verify the connection is alive before or after real work. The description never states when to reach for it (e.g., before a batch of ads_* calls) or what a failure would mean, so an agent must infer the trigger condition.

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