Check server status

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

Beyond the annotations (readOnlyHint, destructiveHint), the description discloses meaningful behavior: it performs one live request to Reddit, reports auth mode, credential acceptance, and the request result. This gives the agent a clear picture of side effects and outputs without requiring schema inspection.

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?

Three sentences with clear front-loading: action, usage, and details. Minor redundancy exists between the first and third sentences (both mention auth mode), but the description remains tight and waste-free overall.

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 diagnostic tool with safety annotations, the description fully covers what it does, when to use it, and what it reports. No output schema exists, but the description lists the key pieces of information returned, which is sufficient for an agent to understand the result.

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 baseline of 4 applies. The description adds no parameter details, but none are needed since the schema is empty.

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 states a specific verb ('Check') and resource (server configuration, auth mode, Reddit connectivity), making its purpose immediately clear. This tool is obviously distinct from the sibling Reddit data tools, as none relate to server health or auth.

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?

Explicit when-to-use guidance is provided: 'Run this first when anything looks broken.' It does not mention when not to use it or name alternatives, but given the tool's unique diagnostic role and unrelated siblings, this is sufficient.

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