create_mural

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions the return value (mural ID + title), but does not disclose side effects (e.g., creating an empty mural), permission requirements, or behavior on invalid roomId. For a mutating creation tool, this is a significant gap.

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, clear sentence that covers the essential action and return value. There is no wasted text, and it is front-loaded with the primary purpose.

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 schema fully documents all six parameters and the description states the return value, the tool is adequately complete. No output schema exists, so mentioning the return is valuable. A slight gap is that it does not describe the state of the created mural (e.g., empty canvas), but this is largely implied by 'create'.

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 baseline is 3. The description adds minimal parameter meaning: 'in a room' maps to roomId, but otherwise it only restates what the schema already conveys. The return value note does not enhance parameter understanding.

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 uses the specific verb 'create' with the resource 'mural' and the location 'in a room', clearly distinguishing it from all sibling tools that create widgets within a mural. It also states the return value (mural ID + title), which further clarifies the purpose.

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 implies its usage context: you need a roomId to create a mural. However, it does not explicitly state when to prefer this over alternatives, such as 'use this before creating widgets' or mention any prerequisites beyond the required roomId. There are no exclusions or alternative tool references.

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