enoch_preflight

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

Annotations include idempotentHint=true and openWorldHint=true, indicating the operation is safe to repeat. The description adds no behavioral details beyond the verb 'run', but this does not contradict annotations. However, it fails to explain what 'preflight' entails (e.g., side effects, state checks).

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 sentence, which is concise and front-loaded. However, its brevity may sacrifice necessary detail given the lack of parameter documentation and contextual guidance.

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 complexity of a worker health check with many sibling tools, the description is incomplete. It does not address return values, error conditions, or how it differs from related tools, leaving the agent underinformed.

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?

With 0% schema description coverage, the description is expected to illuminate the 'payload' parameter, but it does not. The parameter name alone is generic, and no format, constraints, or examples are provided, leaving the agent to guess its purpose.

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 'Run worker health preflight' uses a specific verb and resource, clearly indicating it performs a health check on workers before a flight. It distinguishes itself from siblings like enoch_core_health and enoch_queue_health by specifying 'preflight', implying a preliminary check.

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 provides no guidance on when to use this tool versus alternatives like enoch_core_health or enoch_queue_health. It lacks context on prerequisites, common use cases, or avoidance scenarios, which is critical given the large sibling set.

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