openclaw_nodes_location

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

No annotations are provided, and the description only states 'Get location,' implying a read-only query. However, it does not disclose important behavioral traits such as whether pairing is required, what happens if the node is not paired, or the format of the returned location.

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 description is a single, concise sentence with no unnecessary words. However, given the tool's two parameters and lack of annotations, more detail might be warranted, but it remains appropriately short.

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 tool with two parameters, no output schema, and no annotations, the description is too minimal. It fails to explain what 'paired node' means, the significance of accuracy levels, or what the return value contains. This is insufficient for an agent to invoke the tool correctly.

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 description does not add any meaning beyond the input schema. The schema has 50% description coverage (only 'node' has a description), but the tool description does not explain the 'desiredAccuracy' enum values or the difference between coarse, balanced, and precise.

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 'Get location from a paired node' clearly states the verb (Get) and resource (location from a paired node). It implies a read operation on a specific node, which distinguishes it from sibling tools like openclaw_nodes_camera_snap or openclaw_nodes_status. However, it does not explicitly differentiate itself from all siblings.

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?

No guidance is provided on when to use this tool versus alternatives like openclaw_nodes_status or openclaw_gateway_status. The description does not mention prerequisites (e.g., node must be paired) or conditions for use.

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