ping_site

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

Annotations already indicate safe, idempotent, and external-access operations. The description adds concrete behavioral detail: it connects to a site, verifies authentication, returns user identity and version info, and mentions conditional access ('if accessible'). This goes beyond the generic annotations.

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 a single, front-loaded sentence of 15 words. It conveys the main action immediately and includes essential details without superfluous information. 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?

Given the simple tool (one parameter, no nested objects, output schema present), the description covers the core behavior and return values. However, it does not explain the parameter, which is a noticeable gap. The tool is functional but not fully self-contained.

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?

Schema description coverage is 0%, so the description must compensate. It does not mention the parameter 'site_id' at all, leaving the agent to infer its meaning from the context. No format, required status, or usage details are provided, which is insufficient for a single parameter.

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 clearly states the tool's purpose: 'Verify connectivity + authentication to a WordPress site.' It specifies the verb 'verify' and the resource 'WordPress site.' It also distinguishes itself from sibling tools like check_elementor_versions by combining connectivity and authentication checks with version retrieval.

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: use this to check connectivity and get version info. However, there is no explicit guidance on when to use this tool versus siblings (e.g., check_elementor_versions or list_sites) or when not to use it. The description lacks alternatives or exclusions.

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