elementor_lite_ping_site

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive semantics, so the safety profile is free. The description adds two useful facts beyond that: the call is 'authenticated' (auth is required) and it returns only connection status, which is valuable given there is no output schema.

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?

One sentence, front-loaded with the operation and capped by the return scope. Nothing is wasted and there is no filler.

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?

Auth requirement and the narrow return are covered, and annotations handle safety, but with no output schema and an undocumented required parameter, an agent still lacks the identifier format and error/return shape needed to invoke reliably.

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 single 'site' parameter has 0% schema description coverage, and the description never says what form it takes (ID, URL, slug) or what multiple/zero values mean. With one required undocumented parameter, the description should compensate and does not.

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 states a specific verb ('read') and the exact result ('connection status'), which tells an agent this is a reachability/auth probe rather than a data fetch. It does not explicitly name the 'site' resource or differentiate itself by name from the list_* and summarize_* siblings, but the scope is clear enough to distinguish.

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 explicit when-to-use or when-not-to-use guidance, nor any reference to the sibling tools. The phrase 'return only connection status' implies a cheap pre-flight check, but the agent must infer that this is meant to validate connectivity before other operations.

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