runpod_watch

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

No annotations are provided, so the description fully discloses important behaviors: polling interval (~15s), the auto-stop feature on idle timeout, and that it starts broadcasting LIVE status. No contradictions.

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?

Three sentences, front-loaded with main purpose and key details. Somewhat wordy (e.g., mentioning runpod_pod_connect context), but each sentence adds value. Could be slightly tighter but still effective.

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 simple one-parameter tool with no output schema, the description covers all necessary context: what is watched, refresh rate, idle auto-stop behavior, and distinction from siblings. Fully complete.

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?

Only one parameter (pod_id) with schema description 'The RunPod pod ID to watch.' Schema coverage is 100%, so baseline 3 is appropriate. The description adds no additional meaning beyond what the schema provides.

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 explicitly states it broadcasts a pod's LIVE status (GPU/VRAM, uptime, cost, idle countdown) refreshed every ~15s. It distinguishes from runpod_pod_connect by specifying this tool is for watching without retargeting comfyui-mcp.

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 clear when-to-use context: monitoring a pod that's still booting without retargeting. It also mentions the auto-stop feature, but does not explicitly state when not to use, though the context is clear.

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