vibemk_wait_for_discovery

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

No annotations are present, and the description does not disclose behavior such as blocking, polling, timeouts, or side effects. It is unclear if this tool makes any changes or is purely read-only. The description 'wait until...' suggests blocking but lacks explicit detail.

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 short and front-loaded with an emoji, but it is somewhat redundant: 'Wait for discovery completion' is repeated as 'Wait until service discovery finishes on a host'. This redundancy reduces clarity but the overall length is appropriate.

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 tool's simplicity and the absence of an output schema, the description provides adequate context for basic use. However, it lacks details on expected return value, error conditions, or timeout behavior, which could be important for a waiting operation. This is a minor gap.

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 parameter 'host_name' is described as 'Host name to wait for discovery completion', which clearly explains its role. Since the schema already provides the type and required status, the description adds some semantic value but is not extensive. This aligns with the baseline for full schema coverage.

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 clearly states the tool's purpose: to wait until service discovery finishes on a host. The verb 'wait' is specific and the resource is clear. It distinguishes from siblings like start_service_discovery and get_discovery_status, though it doesn't explicitly name them.

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?

No explicit guidance is provided on when to use this tool versus alternatives. It does not mention sequencing (e.g., 'use after starting discovery') or contrast with get_discovery_status or start_bulk_discovery. The intended usage is implied but not stated.

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