get_map

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait: tile data is summarized by default and only fully included when includeTiles is true. However, it does not describe return format, error handling, or confirm whether the returned map data includes other components like events or properties, leaving some uncertainty.

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 two sentences, front-loaded with the main purpose, and contains no redundant information. It efficiently conveys the core function and the key behavioral note about tile summarization.

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?

The tool has no output schema, so the description should ideally explain what 'map data' includes. It mentions tiles and the ID but does not clarify whether events, properties, or other map components are part of the return. Given the sibling tools, this is a reasonable but incomplete summary for an agent.

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 already provides 100% coverage for both parameters. The description adds value by explaining the default tile summarization behavior, which is not fully clear from the schema's 'Include the full tile data Table (large!)' alone. This clarifies the effect of setting includeTiles to true.

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 tool's function: 'Get map data by ID' and references the file path Data/MapXXX.rxdata. It also indicates that tile data is summarized unless includeTiles is true, which helps distinguish it from tile-specific tools like get_map_tiles. However, it does not explicitly differentiate it from siblings like get_map_events or get_map_infos.

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 description implies usage when you need map data by ID, but it does not state when to use this tool over alternatives. The note about tile summarization provides parameter-level guidance (when to set includeTiles), but there is no explicit exclusion or comparison with sibling tools such as get_map_tiles or get_map_events.

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