ghost_test_connection

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior (verifies authentication and connection), but doesn't state whether the call is non-destructive/safe, what happens on failed auth (error vs. boolean result), or what the return value looks like. The intent is clear, but operational details are missing.

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 zero filler. Both the subject (self-hosted Ghost CMS) and the action (verify authentication and connection) appear immediately, and every word earns 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?

For a zero-parameter, no-output-schema tool with a simple purpose, the description covers the essential context. The only gap is what the agent can expect on success or failure, which would help an agent interpret the result, but the overall simplicity keeps this close to complete.

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 the schema carries no semantics to clarify. Per calibration, a 0-parameter tool receives a baseline of 4; the description correctly adds no parameter information because none is needed.

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?

States a specific verb (verify) and resource (authentication and connection to the Ghost CMS instance). It unambiguously distinguishes itself from the 34 sibling tools, which are all content CRUD operations (posts, tags, members, pages, newsletters), by being the only connectivity/auth-check tool in the set.

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 by naming its action, but it doesn't explicitly frame when an agent should invoke it — e.g., before running other Ghost operations, or when diagnosing connection failures. It also doesn't state alternatives (like attempting a real operation to implicitly validate connectivity), so guidance 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.