mdma_mutate

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

With no annotations, the description carries the full burden and does not disclose whether changes are in-memory only, what save=false leaves behind, whether deletes are reversible, or what errors occur for invalid request/channel names. It also lists 'set_param' as an operation even though the schema's kind enum omits it, which will mislead an agent that tries to pass that value.

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?

A single front-loaded sentence with the resource stated before the operation list; no filler. It is arguably too terse for a 7-parameter mutation tool, but not padded.

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 7-parameter mutation tool with no annotations and no output schema, the description leaves critical gaps: no side-effect or persistence semantics, no error behavior, and an operation list that disagrees with the schema enum. An agent cannot safely invoke it from this text alone.

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 coverage is 100% and each parameter is documented inline, so the baseline is 3. The description adds nothing beyond restating the enum values, and its mention of set_param (absent from the enum but backed by the param/value fields) creates ambiguity rather than clarifying parameter usage.

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 clear verb ('Change') and resource ('MDMA assignments/parameters') and enumerates the supported operations, so an agent knows exactly what domain the tool touches. It does not differentiate from siblings like dma_mutate, gic_mutate, or mdma_query, so a 4 rather than a 5.

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?

No guidance on when to use this versus mdma_query (read) or dma_mutate/gic_mutate, and no prerequisites such as needing an open project. The only usage hint is the parenthetical operation list, which is implied context at best.

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