baker_set_settings

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

Annotations already declare a non-read-only, non-destructive, closed-world write operation. The description adds scope by listing the exact settings affected and their allowed enum values, but it does not explain whether settings are merged or replaced, whether omitted settings are preserved, or how the change affects subsequent bakes.

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 a single dense sentence that front-loads the purpose before enumerating settings. It contains little waste, though the long comma-separated list is less scannable than it could be.

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 complex, free-form nested `settings` object and 0% schema description coverage, the enumeration of settings keys is helpful. Still, the description omits the `baker` parameter and does not clarify partial-update versus replacement semantics, leaving meaningful ambiguity for an agent invoking the tool.

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 the description must carry parameter meaning. It does a reasonable job enumerating many keys inside the free-form `settings` object and clarifying enum values for outputBits, edgePadding, tileMode, and geometryMode. However, it never mentions the `baker` parameter, leaving one of the two top-level parameters undocumented.

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 a specific verb and resource: 'Set bake project settings.' It also enumerates many of the configurable fields, making the tool's scope concrete. However, it does not distinguish this tool from nearby siblings such as baker_set_maps, baker_set_cage, or baker_save_preset.

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?

The description provides no explicit guidance on when to use this tool versus alternatives, nor does it state prerequisites or ordering relative to baking. Usage is only implied by the tool name and the list of settings.

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