stop_background_command

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

No annotations; description only says 'stops' without elaborating on signal sending, process termination behavior, or side effects. Input schema reveals signal parameter but description doesn't mention it.

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 concise sentence, but phrasing 'Stops through Colab Terminal' is slightly awkward. No unnecessary words, but could be clearer.

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?

Minimally covers core action for a simple tool. Lacks details on error states, prerequisites (command must exist), or return behavior, but may suffice for basic usage.

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?

Schema covers both parameters with 100% description coverage. Description adds no extra meaning; doesn't mention signal parameter or provide context beyond what schema already states.

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?

Clear verb 'Stops' and resource 'background command'. Links to sibling 'start_background_command' distinguishes it from starters but lacks explicit differentiation from other background command tools like watch or 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?

Implies use only for commands started by start_background_command, but provides no explicit when-to-use vs alternatives or caveats. No guidance on when not to use this over other sibling tools.

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