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

Adds useful behavior beyond annotations: changes apply instantly, cost no credits, use partial updates, and return the same fields as get_market_map. It does not explain reversibility or overwrite semantics for existing style settings, but destructiveHint=true already signals mutation risk.

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?

Front-loads the core action and packs the option list efficiently. It is dense but every clause carries parameter or behavioral information, with only a minor cost in readability from the long enumerating sentence.

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?

Covers the essential behavior for a mutation tool with no output schema by noting partial updates, instant application, account requirement, and return shape via get_market_map. It could be stronger if it clarified whether unspecified settings remain unchanged, but the core invocation context is 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 coverage is low at 38%, but the description compensates by enumerating the allowed values for every styling parameter: theme, columns, logo style, density, logo shape, logo size, and greyscale. This gives an agent enough semantic detail to choose values without relying on enum labels alone.

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?

States a specific verb and resource: changing how an existing market map looks. It distinguishes itself from create/edit/publish siblings by describing appearance-only restyling with the same settings as the Market Map Maker style menu.

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?

Clearly indicates partial-update usage with 'Pass only what should change' and notes the free account requirement. It does not explicitly compare to edit_market_map or state when not to use this tool, so it falls short of full when/when-not guidance.

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