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

Beyond the annotations (readOnlyHint=false, openWorldHint=false), the description fully discloses that it modifies the drive vector, increments generation, appends an audit row in a transaction, and returns the new vector. No contradictions.

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?

Two sentences with no filler. Critical constraints (clamped delta, transaction, return values) are front-loaded. Every sentence adds value.

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 0% schema coverage and no output schema, the description explains the tool's core function and return values. It omits explicit mention of the output format (e.g., vector of 5 numbers and generation number), but the context is sufficient for an agent to use it correctly.

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 0%, so description must compensate. It explains that all five numeric parameters represent per-axis deltas clamped to ±0.05, which is accurate. However, it doesn't map each parameter to its corresponding drive axis (e.g., mastery, solitude), which would be useful.

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 clearly states the tool applies a clamped delta to the drive vector, increments generation, and appends an audit row. It specifies the resource and action distinctly from sibling tools like set_soul or record_skill_outcome.

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?

Explicitly advises 'Use after a reflection produces a drift signal,' giving clear context. No explicit when-not-to-use or alternatives, but the tool is specialized enough that this guidance is sufficient.

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