hac_spartacus_doctor

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

No annotations are provided, so the description carries the full behavioral burden, and it does not disclose whether the check is read-only, whether it needs a running storefront or admin credentials, how long it takes, or what happens on failure. The word 'health check' weakly implies a non-mutating probe, but nothing is stated. No contradiction with annotations exists since none are supplied.

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?

A single, front-loaded sentence with no filler or repetition. It is efficient, though its brevity is partly under-specification rather than deliberate compression.

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?

An output schema exists, so return values need not be explained, but the definition is still thin for a multi-target diagnostic: it never clarifies the role of storefront_url vs site_id, the language parameter, or dependency requirements. Given three fully undocumented parameters and no annotations, the description leaves significant gaps.

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?

All three parameters (lang, site_id, storefront_url) have 0% schema description coverage and are not mentioned anywhere in the description. The description adds no meaning beyond the bare property names and default values, leaving the agent to guess at formats such as the expected URL or language codes.

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?

States a specific verb and scope: 'Performs a full headless readiness health check for a Spartacus storefront and Commerce Cloud BaseSite.' An agent can tell this is a diagnostic/readiness tool. However, it does not differentiate itself from nearby diagnostics such as hac_status, hac_self_diagnose, or hac_b2b_org_doctor, so a 5 is not warranted.

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 explicit when-to-use guidance, no prerequisites, and no named alternatives among the many doctor/status/diagnose siblings. The reader must infer that this is used to verify headless readiness, but nothing states when to prefer it over hac_b2b_org_doctor or hac_status.

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