Add Map Theme

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

With no annotations, description carries full burden. It discloses the create/update behavior and the source (current layer visibility). However, it does not mention return values, side effects on existing themes, or permissions needed. Adequate for a simple tool but could be more detailed.

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?

Two concise sentences convey essential information without fluff. Could include slightly more detail without being verbose, but remains efficient.

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 a single parameter and no output schema, description covers the basic action and update rule. However, it omits context like whether themes are project-level or file-based, and does not specify the effect on the current view. Adequate for a simple tool but not fully complete.

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 description coverage is 0%, so description must compensate. It indirectly explains the 'name' parameter as the theme identifier by stating it will be updated if it exists. However, no further details (format, constraints) are provided, leaving the parameter underspecified.

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 or updates a map theme from the current layer visibility state, using a specific verb and resource. It distinguishes itself from siblings like apply_map_theme (which applies an existing theme) and remove_map_theme (which removes one).

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?

Description implies when to use (to save current visibility) but does not explicitly contrast with alternatives like apply_map_theme or remove_map_theme. No explicit guidance on when not to use or prerequisites.

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