omni_ping

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the call requires no authentication and returns service info, protocol version, and auth requirements. This is sufficient for a liveness probe, though it does not mention side-effect-free behavior explicitly.

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 two short sentences with no wasted words. The purpose is stated first, followed by a critical behavioral note about auth and the expected return contents.

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 liveness probe with no output schema, the description provides enough context: what it probes, that auth is not needed, and what it returns. It lacks an explicit statement about when to use it in agent workflows, but the simple nature of the tool makes this a minor gap.

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 zero parameters, so parameter semantics are not applicable. The schema is effectively empty, and the description correctly avoids inventing parameter details. Baseline for 0 parameters is 4.

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 names a specific verb and resource: 'Liveness probe for the OmniMod Agent Dev Link bridge.' It clearly identifies this as a health-check endpoint and distinguishes it from sibling tools by specifying the bridge as the target.

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?

The description implies usage as a liveness check and explicitly notes 'NO AUTH,' but it does not state when an agent should prefer this over sibling tools like omni_pair or omni_state. The context is implied rather than explicit.

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