start_gpu_monitor

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

The description mentions 'background sampler' and output format but does not disclose that it runs until explicitly stopped, resource consumption, or potential side effects. Without annotations, more behavioral detail is needed.

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 concise sentence that is easy to parse. However, it could be slightly longer to include parameter details without losing conciseness.

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 no annotations, no output schema, and three undocumented parameters, the description is incomplete. It does not explain how to stop the monitor, how to read the output, or the relationship with sibling tools like read_gpu_monitor.

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 description does not mention any of the three parameters (name, intervalSeconds, savePath). Since schema description coverage is 0%, the description should compensate by explaining these parameters, but it fails to do so.

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 starts a lightweight nvidia-smi background sampler that writes timestamped JSONL samples. This specific verb-resource combination distinguishes it from sibling tools like sample_gpu_usage (one-time sample) and check_gpu (status 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 implies usage for continuous GPU monitoring but does not explicitly state when to use this vs alternatives. No guidance on prerequisites or when not to use is provided.

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