download_robot_map_v1

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

No annotations are present, and the description does not disclose important behavioral details such as whether the download is synchronous, file format, size limits, or authentication requirements. The agent lacks context on side effects or expected behavior.

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 brief (under 30 words) and includes an Args/Returns section for structure. However, it could be more concise by omitting the trivially obvious lines and instead providing critical details.

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?

Given no output schema, the description should clarify the return structure, but it only states 'dictionary containing the map download information,' which is ambiguous. Lacks details on error handling, file content, or further processing steps.

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 input schema has 100% coverage (1 parameter, map_id), but the description only repeats that it is 'The ID of the map to download' without adding meaning beyond the schema. No information on allowed values, format, or source for the ID is provided.

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 clearly states the action (downloads) and resource (robot map) along with API version (V1). However, it does not distinguish from the sibling tool download_robot_map_v2, which likely has a different purpose or behavior.

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 download_robot_map_v2. There is no mention of prerequisites, scenarios, or limitations.

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