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

No annotations are provided, so the description carries the full burden. 'Connectivity test' provides almost no behavioral insight—it doesn't say whether the tool makes network calls, what it returns, or whether it has side effects. This is a serious gap for a tool with no structured metadata.

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?

The description is only two words, which is concise in length but severely under-specified. It does not provide useful structure or details, making it more of an under-specification than effective conciseness.

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 simple tool with no parameters and no output schema, one might expect minimal description, but 'Connectivity test' still leaves critical gaps such as what is being tested, how to interpret the result, and any side effects. Given the sibling tools (health_check, region_status), more context is needed to distinguish and use this tool effectively.

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 has 0 parameters and an empty schema, so there is nothing to describe. The baseline for 0-param tools is 4, and the description doesn't need to compensate for any undocumented parameters.

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 'Connectivity test' clearly indicates the tool checks connectivity of some kind, but it lacks a specific verb+resource structure and does not differentiate from siblings like health_check or region_status. It is not a tautology, but it is vague.

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?

There is no guidance on when to use this tool versus alternatives. No prerequisites, context, or exclusions are mentioned, making the usage context entirely implicit.

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