Stop the program

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so the mutating-but-safe profile is covered structurally; the description adds real value by naming the concrete effects (worker terminated, wheels stop). It does not say what happens when no program is running, though the idempotent hint largely covers that.

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?

A single parenthetical-bearing sentence with zero waste, front-loading the action and following with the effect. Nothing could be removed without losing information.

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?

For a zero-parameter control tool with no output schema and safety already covered by annotations, the definition supplies everything needed to invoke it correctly. The only residual gap, its relationship to the sibling 'stop', is a usage-routing concern scored elsewhere.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Schema coverage is reported at 100% with an empty properties object, so no gap exists.

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?

States a specific verb and resource ('stop the running rover program') plus the observable outcome, so the agent knows exactly what it does. It does not distinguish itself from the sibling tool 'stop', which reads as a near-synonym and could be confused with this one.

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?

Usage is only implied by 'running program' — the agent must infer it is the counterpart of run_program. There is no explicit when-to-use/when-not, and no routing guidance against the sibling 'stop', even though that ambiguity is the most likely selection error here.

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