get_map

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

With no annotations, the description carries full burden: it doesn't say whether this is a read-only fetch, whether results are cached, what the 'refresh' flag actually triggers, or whether permissions/robot connectivity are required. Only the bare payload ('maps with their regions') is disclosed.

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?

Very short with no filler, but it is a fragment rather than a front-loaded sentence and omits the verb, leaving the agent to infer 'retrieve' from the name alone.

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?

An output schema exists, so return values needn't be explained, and the tool is a single optional parameter. Still, the purpose of 'refresh' and the read semantics remain unexplained, which leaves a meaningful gap for even this simple tool.

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 coverage is 0% for the single 'refresh' parameter, and the description never mentions it — the agent cannot tell whether refresh forces a re-fetch from the robot or returns stale cached maps. The description adds nothing beyond the property name.

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 the resource and its content ('smart maps with their regions'), which distinguishes it from the other read siblings like get_settings or get_robot_info. The verb is only implied by the name, but the payload is specific enough to select the tool.

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 phrase 'for use with start_clean' hints at a prerequisite relationship, suggesting maps are retrieved to pick a target before starting a clean. It gives no explicit when/when-not or alternatives, so the guidance is implied rather than stated.

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