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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'status' and 'checks' which imply read-only behavior, but it does not explicitly state that the operation is non-destructive, what kind of output to expect, or whether any side effects or permissions are involved. This is a minimal disclosure, but the inference of a passive health check is fairly strong.

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 a single concise sentence that front-loads the tool name and core purpose. Every word earns its place, and there is no filler or redundant information. It is appropriately sized for a simple tool with no parameters.

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 tool's simplicity (no parameters, no output schema), the description covers the basic purpose: checking DORAOracle server status and backend connectivity. However, 'all backend connectivity checks' is vague—it does not enumerate which backends or what kind of status reporting is done. A bit more detail on the scope or output would make it more complete, but it is not critically inadequate.

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 description has no need to explain parameter semantics. The baseline for 0 parameters is 4, and the description appropriately focuses on the tool's purpose without irrelevant parameter details.

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 'DORAOracle server status and all backend connectivity checks' clearly identifies the tool's function as checking server and backend health. It distinguishes this from sibling tools like cve_search or breach_check by focusing on infrastructure status rather than security data. However, it lacks an explicit verb, making it a noun phrase rather than an action statement.

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 usage guidance is provided. The description does not state when to use this tool versus alternatives, nor does it mention contexts where it should be avoided. The purpose is implied but there is no explicit 'use this when' or 'for X use sibling tool Y'.

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