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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower; the description nonetheless adds real operational context: existing files are replaced, the size ceiling is 50 MB, and a large file may take about a minute. That latency and limit information is genuinely useful for planning. It does not mention permission requirements or what happens on failure.

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?

Dense and front-loaded: the overwrite behavior and the muse_chat handoff come before secondary details like size limits and the POST /files endpoint. Every clause carries information, though the trailing HTTP endpoint reference adds little for an agent choosing a tool.

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 five-parameter write tool with full schema coverage and annotations covering the safety profile, the description is nearly complete: it covers overwrite behavior, encoding options, limits, and latency. The one gap is return semantics — there is no output schema and the description never says what the call yields (e.g. the stored path or file id), which the agent needs for the subsequent muse_chat step.

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 100%, so the schema already documents all five parameters, including the content/contentBase64 split. The description largely restates that split and adds only the 50 MB constraint, which does not map to a single parameter. Baseline 3 is appropriate when the schema carries the weight.

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 (write a file into the Muse workspace) and clarifies overwrite semantics for an existing path. It also names the downstream handoff tool, muse_chat, so the agent understands the write is prep for a chat reference. It stops short of explicitly contrasting with siblings like muse_read_file, muse_delete_file, or muse_upload_asset.

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?

Gives a concrete usage scenario — writing a document, data, or code file for the agent to use, then sending its path in muse_chat with an example prompt. That is clear positive guidance with a worked example. It offers no exclusions (e.g. when to prefer muse_upload_asset for binary assets) and no stated prerequisites for the call.

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