validate

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

Explicitly states 'read-only', 'Changes nothing', and describes return format (pass/warn/fail, ok true only when nothing failed). Full disclosure without annotations.

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?

Single sentence front-loads purpose but is somewhat dense. Could be split for readability, but still efficient.

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?

Complete description for a parameterless tool with output schema. Covers scope, checks, and return criteria.

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?

No parameters; schema coverage is 100% by default. Description adds value by explaining what the tool checks without needing parameters.

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?

Description clearly states 'read-only readiness check of the whole fleet' with specific areas (SSH, service, binary, disk, RPC, cores, RAM, disk, toolchain, DNS credential presence). Distinguishes from sibling tools like 'fleet_status' or 'node_detail' by focusing on readiness validation.

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?

Implicitly clear that it's for pre-deployment readiness checks. Context of sibling tools (e.g., 'fleet_status', 'plan_node_upgrade') suggests when to use. But missing explicit when-not or alternatives.

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