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. 'Liveness.' does not state whether this is a read-only check, what it returns, whether it performs any side effects, or what conditions could affect its behavior.

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 extremely short, but this is under-specification rather than effective conciseness. 'Liveness.' conveys almost no actionable information, so the single word does not earn its place in helping an agent use the tool.

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 there are no parameters, no output schema, and no annotations, the description should at least clarify what liveness means (e.g., returns OK, checks server status, etc.). The current description is incomplete for an agent to correctly interpret the tool's purpose or 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 schema has zero parameters, so the schema provides no information to compensate. However, the tool requires no input at all, meaning parameter semantics are trivially minimal; a 4 is reasonable because nothing meaningful could be added for a no-parameter tool.

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 'Liveness.' is a tautology that essentially restates the tool name 'health' without specifying what action it performs or what resource it operates on. It gives an agent no concrete indication of what invoking this tool will do or return.

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?

There is no guidance on when to use this tool versus any alternative. The context signals show zero parameters and no annotations, and the description does not explain what 'Liveness' means in practice or when an agent should call it.

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