stop_navigation

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

No annotations are provided, so the description carries the full behavioral burden, and it delivers almost nothing: it does not state whether in-progress navigation is cancelled or merely halted, whether the robot stops in place, whether this is safe/persistent, or whether robot_sn must be online. Only the bare action is conveyed.

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 text is minimal, but this is under-specification rather than conciseness. The two-language duplication adds no information, and nothing about scope, effect, or prerequisites is front-loaded because nothing is present at all.

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 command-executing mutation tool with no annotations, no output schema, and an undocumented required parameter, the definition is far too thin. An agent cannot determine the effect on the robot's state or how to confirm success, so key context is missing.

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 schema has 0% description coverage and the description says nothing about robot_sn. While the single parameter's meaning (robot serial number) is inferable from its name, it is the only required argument and the definition never explains which robot identifier format is expected or whether it must match an active navigation command.

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 is a bilingual literal restatement of the tool name ('stop_navigation' → '停止导航 / Stop navigation'). It names no resource context, no scope, and does not differentiate from close siblings such as pause_navigation, resume_navigation, or navigate_home. This is the textbook tautology case.

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?

There is no guidance on when to call this versus pause_navigation (interruptible) or stop_task (tasks vs navigation). No prerequisites, no conditions, no alternatives are mentioned, so the agent must infer usage entirely from the name.

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