satellite_stop_decoding

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

With no annotations, the description carries the full disclosure burden, and it does contribute one valuable behavioral fact: the radio is returned to Python control, i.e., SDR ownership is released after the call. It omits error behavior when nothing is running and whether partially decoded data is preserved or discarded, which matters for an early-abort operation.

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 front-loaded sentence with the action first and the side effect second; every clause carries information and there is no filler.

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 stop tool with no output schema, the description covers the core action and the resulting state transition. Only edge-case behavior (no active decode, partial data) is left unstated.

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 no parameter semantics to explain and no schema gap to compensate for. Baseline 4 applies.

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?

"Stop the running Meteor-M decode" is a specific verb+resource and names the Meteor-M mode, which distinguishes it from pager_stop_decoding, aviation_stop_tracking, and marine_stop_tracking. It does not explicitly name satellite_decode_meteor as the counterpart, but the satellite prefix and the mode name make selection unambiguous.

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 word "early" implies the use case is aborting a decode before it completes naturally, which is useful implicit guidance. However, it never states what happens if no decode is running, whether letting the decode finish is preferred, or how this relates to satellite_decode_meteor.

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