pine_ping

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

With no annotations provided, the description fully discloses behavior: no side effects, connection details (Unix socket or TCP with fallback), timeout (10 seconds), and return format. This meets the burden of transparency completely.

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 well-structured with clear sections (PURPOSE, USAGE, BEHAVIOR, RETURNS). Every sentence serves a purpose without redundancy, making it concise yet informative.

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 no parameters and no output schema, the description covers all necessary aspects: purpose, usage timing, behavioral details, and return value. It is fully self-contained and complete for an agent to use.

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?

There are no parameters (input schema is empty with 100% coverage). The description adds no parameter info, but for a parameterless tool, it provides sufficient context about what the tool does, exceeding expectations.

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 'Verify the PINE server (PCSX2) is reachable and responding,' providing a specific verb and resource. It distinguishes itself from sibling tools like pine_read16 or pine_write16, which are for data access, by being the liveness probe.

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?

Explicitly advises 'Call once at session start before other tool calls,' giving clear usage context. It also notes that it doubles as an emulator-version sniffer. While it doesn't specify when not to use it, the tool is narrow in scope, so this is adequate.

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