evolve

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

Annotations already flag destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the mutation profile is covered structurally. The description adds 'update personality' but does not disclose what state is overwritten, whether changes are reversible, or what 'evolution' concretely does, so its added behavioral value is thin.

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?

It is a single short sentence with no wasted words, which is good, but the front-loaded phrase 'Universal Primitive' spends the prime real estate on jargon rather than the actionable verb.

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?

An output schema exists so return values need not be explained, but for a non-idempotent, destructive mutation tool with two undocumented parameters, the description is far too thin to describe effects, scope, or preconditions.

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% across two parameters, and the description offers no explanation of 'instruction' or 'user_id'. The agent gets no semantics for the required instruction field or the user scoping, so the description fails to compensate for the coverage gap.

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 rough verb+resource: 'update agent personality' gives a hint of what happens. But the framing 'Universal Primitive' is unexplained jargon and 'triggering evolution' is vague and undefined, so an agent cannot confidently tell this apart from siblings like dream, wake_up, or forget.

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?

There is no when-to-use, when-not-to-use, or alternative guidance at all. Given six semantically overlapping siblings (dream, think, forget, wake_up, memory_hook, project), the absence of routing guidance is a clear gap.

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