project_settings_write

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

No annotations are provided, so the description carries the full behavioral burden. It usefully says the output is a new 3MF and that meshes, painting, and unknown members are preserved, but it does not explain overwrite behavior, permissions, failure modes, or how expected_source_sha256 protects against concurrent source changes.

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 front-loaded sentence with no wasted text. It is appropriately concise, though the brevity contributes to the missing usage and parameter detail assessed elsewhere.

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?

This is a complex write tool with five parameters, a nested changes object, and a required expected_source_sha256, but the description only states the high-level operation. The output schema means return values need not be explained, but the parameter and safety behavior remain materially incomplete.

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% across five parameters, including required source, destination, changes, and expected_source_sha256. The description does not mention any parameter names or explain what changes, remove, or the SHA-256 guard mean, so it does not compensate for the schema gap.

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 states a specific verb and resource: writing project settings to a new 3MF, and adds that meshes, painting, and unknown members are preserved. It is clear what the tool does, but it does not explicitly distinguish itself from related siblings such as project_target_settings_write or settings_write.

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?

There is no guidance on when to use this tool versus settings_write, project_target_settings_write, or project_metadata_write. It also omits prerequisites such as whether the destination may already exist or when the SHA-256 guard is required.

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