project_metadata_write

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

With no annotations, the description carries the full safety burden and does disclose useful behavior: it replaces existing metadata, produces a new 3MF, requires reading the original member first, and only checks XML/JSON syntax while OrcaSlicer validates semantics later. It still omits details about the expected_source_sha256 guard and overwrite behavior at destination, leaving some mutation-risk context unstated.

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 three tight sentences with the action front-loaded, followed by the prerequisite and validation warning. Every sentence adds useful information without repetition.

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?

The output schema means return values need not be explained, and the description gives useful framing for a format-level mutation. But for a 5-parameter write operation with no annotations and zero schema descriptions, it leaves too much unsaid about parameter roles and guardrails to be 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% for 5 required parameters, so the description must compensate. It only hints at source/destination and metadata member conceptually; it does not explain text format expectations or, importantly, what expected_source_sha256 is for.

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: replace existing JSON/XML metadata in a new 3MF, including object/plate settings. It is clear what the tool does, though it does not explicitly distinguish itself from nearby mutation siblings such as project_settings_write or project_target_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?

It gives a prerequisite (read the original member first) and frames the operation as expert/format-level, which implies caution. However, it does not say when to use this instead of project_settings_write or other project mutation tools, nor when not to use it.

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