navigate_home

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 delivers essentially nothing beyond the action name. It does not disclose whether the call blocks or returns a command to poll (the presence of wait_for_command and get_command_status siblings makes this a real question), what happens if a task is running, or whether the robot must already be localized on the given map.

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?

It is a single front-loaded phrase with no padding, which is structurally sound. However the bilingual duplication consumes space without adding information for the agent, and the brevity reflects under-specification rather than disciplined 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?

With no annotations, no output schema, and three undocumented parameters, the description is far too thin for a robot-command tool. An agent has no way to know the return contract, blocking behavior, or failure modes from either the description or the structured fields.

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 description coverage is 0% across three parameters, and the description adds no parameter meaning at all. The field names (robot_sn, map_id, map_resource_id) are largely self-explanatory, but the description does not clarify why map_resource_id is optional, when it is needed, or how map_id relates to it.

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 pairs a clear verb (navigate) with a specific destination (the charging point / home), so an agent knows exactly what the call accomplishes. It stops short of distinguishing itself from navigation-adjacent siblings such as pause_navigation, stop_navigation, or task-driven movement.

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 when-to-use guidance, no stated prerequisites (e.g. robot must be idle, no active task), and no mention of the competing navigation-control siblings. The agent is left to infer that this is distinct from start_task/stop_navigation on its own.

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