Backlog health

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

With no annotations, the description carries the full behavioral burden. It discloses that the call is a non-destructive health/connectivity check and implies it is safe to run pre-mutation, but it does not describe what happens when the API is unhealthy (error vs. status result) or what the response contains. For a trivial read-only probe this is adequate, not rich.

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?

One eight-word sentence with zero filler. The core action ('checks health and connectivity') is front-loaded, followed immediately by the usage condition ('before mutations'). 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?

Given the tool's minimal complexity (no parameters, no output schema, no annotations), the description covers the purpose and timing adequately. The only notable gap is return-value semantics or failure behavior, which an agent would need to learn from the live response, but for a zero-config health probe this is a minor omission.

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 there is nothing for the description to clarify beyond the baseline of 4. Schema coverage is trivially 100% on an empty schema, and no parameter documentation 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?

The description names a specific verb ('Checks') and resource ('backlog API health and connectivity'), and the 'before mutations' phrase positions it as a pre-flight diagnostic. This clearly distinguishes it from siblings like backlog.version (version retrieval) and backlog.get_project (data lookup).

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?

'before mutations' tells the agent explicitly when to invoke this tool, providing clear usage context. It does not name alternatives or state when not to use it (e.g., that backlog.version might also probe connectivity), so it stops short of a 5.

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