noetic.mutate

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

With no annotations provided, the description carries the disclosure burden and does contribute that the operation is governed and requires specific authorization context. It still leaves unspecified what happens on success or failure, whether the request is asynchronous, and what side effects occur to the target.

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 filler, and the parenthetical adds useful prerequisite information. It is concise, but it is under-specified for a 4-parameter tool with no schema descriptions, so it is not fully 'appropriately sized'.

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 four undocumented parameters, zero required fields, no annotations, no output schema, and a large sibling set, the description provides only governance prerequisites. It is not complete enough for an agent to invoke the tool correctly, though it at least frames the authorization context.

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% and the description does not explain target, newLabels, sessionId, or contribution. Even the vague mention of 'intent' and 'authority policy' does not map clearly to any parameter, so an agent cannot infer meaning, format, or relationships among the four parameters.

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 identifies a concrete action (requesting a governed change) and adds useful qualifiers: it needs mutate right, intent, and authority policy. This moves beyond the bare name 'mutate' and hints at why it differs from read-only or ungoverned tools. However, it does not specify the domain/resource being changed or explicitly contrast it with similar sibling tools like noetic.propose or noetic.commit.

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 states prerequisites for invocation (mutate right, intent, authority policy), which tells an agent when it is permitted to call this tool. It does not provide when-not-to-use guidance or point to alternative tools when those prerequisites are absent, so the usage guidance is implicit rather than explicit.

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