agent_ping

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

With no annotations provided, the description carries the full burden and does so well. It discloses the state-changing nature, the refusal condition, that the call acts as the local credential-store identity, and that returned content is untrusted data whose instructions must not be followed.

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 four compact sentences, front-loaded with the action, followed by permission gating, identity context, and a security warning. Every sentence contributes necessary information without waste.

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 zero-parameter interface and the presence of an output schema, the description covers what an agent needs: what the tool does, when it is permitted, how it authenticates, and how to treat the response. No critical context is missing.

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 input parameters, so there are no parameter semantics to clarify. The description appropriately adds no parameter detail, which matches the baseline for a parameterless tool.

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 uses a specific verb and resource: 'Send a heartbeat so other agents see this identity as online.' It clearly states the tool's purpose, though it does not explicitly distinguish itself from the sibling tool agent_ping_check, which likely has a related but different 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?

It gives a clear prerequisite and default behavior: 'Off by default: refused unless the human owner set VOIDLY_MCP_RELAY_ALLOW_STATE_CHANGES=1.' This tells the agent when the tool will succeed versus fail, but it does not name an alternative tool or say when to prefer this over other heartbeat or presence mechanisms.

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