artificer-status

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

No annotations are provided, so the description carries the behavioral burden. It fairly thoroughly enumerates what is checked, which implies a non-mutating health check, but it never explicitly states that the tool only reads state or what kind of result the agent should expect. The safety profile is implied rather than stated.

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 dense sentence that front-loads the core purpose ('Health check') and then itemizes the checks, closing with an actionable call-time directive. Every part is informative and there is no filler.

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 zero-parameter diagnostic tool, the description conveys what the tool inspects and when to call it, which is sufficient for an agent to invoke it appropriately. The absence of an output schema and explicit return-format details is a minor gap, but the listed checks compensate reasonably well.

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 accepts zero parameters and the schema coverage is effectively complete. There is nothing for the description to clarify about parameters, so it correctly loses no points and gets the zero-parameter baseline of 4.

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 opens with 'Health check' and clearly identifies the resource (ComfyUI/Artificer environment) plus the specific aspects monitored: reachability/version, VRAM, queue depth, pinned-workflow integrity, and required-model presence. This makes it immediately distinguishable from the sibling generation tools.

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 description explicitly says 'Call this first when generation misbehaves,' giving a concrete trigger and ordering recommendation. It doesn't mention exclusions or alternatives, but for a diagnostic status tool without natural siblings, the guidance is clear enough.

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