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

With no annotations provided, the description carries the burden and it does well: it discloses read-only safety, host affinity, and the public Vercel failure mode. It does not describe the full return payload, but that gap is minor for a zero-parameter snapshot tool.

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 entire description is a single, front-loaded sentence that packs the environment, safety, resource, host, and Vercel behavior. Every phrase earns its place with no padding.

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 no-parameter, no-output-schema local status tool, the description covers purpose, environment, safety, and a key platform-dependent behavior. It could mention what 'available' refers to or differentiate from forge_status, but it is largely complete for selection purposes.

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 and 100% schema coverage (empty schema), so the baseline is 4. The description adds no parameter-specific detail, but 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?

The description uses a specific verb phrase ('Read-only ... snapshot') and names the exact resource ('always_on/loop_health' on the operator's ADP host). It also distinguishes the tool from siblings by stating it is a local ops tool and 'not a portable product tool.'

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 label '[Local ops]' immediately signals the intended environment, and the explicit warning 'Not a portable product tool' tells agents when to avoid it. It also notes a key context condition ('returns available:false on public Vercel'), but it does not name a specific sibling alternative such as forge_status.

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