Apply Map Theme

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

The description adds the behavioral context that it 'restores the layer visibility state', which matches the idempotentHint annotation. No contradictions, but no additional depth beyond what annotations already signal.

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 one efficient sentence with no unnecessary words. It is front-loaded with the primary action and includes a clarifying clause.

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 the low complexity (one required parameter, idempotent annotation, no output schema), the description is mostly complete. The only gap is the lack of explicit parameter description, but the tool name and title together make it clear.

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%, so the description must clarify the parameter. The description does not explicitly describe the 'name' parameter; it is implied from context. This is insufficient for a required parameter with no schema description.

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 applies a map theme and explains what that means: restoring layer visibility state. It distinguishes from siblings like add_map_theme or get_map_themes.

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?

It implies usage context (you must have a theme saved) but does not explicitly state when to use vs. alternatives or when not to use. No exclusions or prerequisites mentioned.

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