create_multi_layer_map

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

Description discloses return structure (filepath, layer_count, title) and the interactive toggle feature, but does not mention permissions, rate limits, or side effects. No annotations are present, so the description carries the burden for behavioral disclosure, but it misses some aspects like whether the tool saves files or requires authentication.

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 extremely concise: two sentences plus a return format list, all front-loaded. No unnecessary words, every sentence earns its place.

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 description covers the main purpose, layer structure, and return values. However, it lacks details on theme options, filename formatting, and data preparation requirements. Despite having an output schema (implied), minor gaps remain for a fully self-contained definition.

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 adds meaningful structure for the 'layers' parameter beyond the schema's 'List of layer dicts', specifying fields like data, name_column, value_column, label, colorscale. Other parameters have adequate schema descriptions, so the description provides additional valuable context.

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?

Description clearly states it creates a multi-layer choropleth map with toggle buttons, distinguishing it from sibling map tools like create_bubble_map or create_serbia_map. However, it lacks an explicit verb like 'Creates', but the noun phrase implies creation.

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 explicit guidance on when to use this tool versus alternatives like create_bubble_map or create_serbia_map. The description implies it's for multi-layer choropleths, but does not specify when not to use it or mention any prerequisites.

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