Ping Obsidian Server

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

With no annotations supplied, the description carries the entire behavioral burden, and it discloses almost nothing beyond the stated purpose. It does not say whether the call is read-only/side-effect free, whether the Obsidian Local REST API requires an API key for this endpoint, what the result looks like (no output schema exists), or how failures are surfaced. For a zero-risk probe these gaps are modest but real, and nothing beyond the one-line intent is conveyed.

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?

A single front-loaded sentence with no filler or redundancy. It is appropriately sized for a trivial probe, though one additional clause about the expected result or auth requirement would have earned 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?

The tool is simple: no parameters, no nested objects, no output schema, and the description states the full intent. Completeness is only slightly short because, absent annotations and an output schema, the agent gets no signal about return shape, authentication, or error behavior.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no inputs are needed, consistent with the empty schema.

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 ('Check') and a precisely scoped resource ('the Obsidian Local REST API server is accessible'), which is a connectivity probe rather than a data operation. That makes it implicitly distinguishable from every sibling, all of which are note/folder/tag/vault operations. It stops short of 5 only because it doesn't explicitly frame itself as the health-check sibling in the toolset.

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?

No explicit when-to-use or when-not-to-use guidance is given, nor any mention of calling it before other tools or after a failure. The intended usage (verify the server is reachable before attempting note operations) is strongly implied by the word 'accessible' but must be inferred by the agent.

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