Remove Map Theme

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

The description says 'Remove', which matches the destructiveHint annotation. However, it does not disclose additional behaviors such as whether the removal is permanent or what happens if the theme is in use.

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?

A single, clear sentence that conveys the essential information without any extraneous content. Front-loaded and 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?

For a simple delete operation with one parameter, the description and annotations together are fairly complete. The destructiveHint covers the side effect, and no output schema is needed. Could add a note about error behavior if the theme doesn't exist.

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 has 0% parameter description coverage and only shows a 'name' string. The description adds 'by name', which provides minimal extra meaning. The agent might benefit from clarification on the expected format or case sensitivity.

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 ('Remove'), the resource ('map theme'), and the required identifier ('by name'). It distinguishes from sibling tools like add_map_theme and apply_map_theme.

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 vs alternatives, or any prerequisites like needing the theme to exist. The description is minimal but functional.

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