memkernel_fenced_append_decision

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

With no annotations, the description carries the full burden, and it does disclose genuine behavioral traits: the holder/token/expiry check shares the append's transaction (atomicity), and it explicitly scopes the guarantee ('protects the memory event; it does not write or lock the file'). It omits failure behavior and auth requirements, but the atomicity and scope disclosure is substantive.

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?

Front-loaded with the action and its precondition in the first sentence, then a compact explanation of the mechanism. It is short and wastes little, though the second sentence's phrasing ('it does not write or lock the file') is terse enough to be slightly cryptic.

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, and the fencing/atomicity semantics are covered. But for a lease-fenced, transaction-scoped mutation with five undocumented parameters, the description leaves failure modes, parameter meanings, and the relationship to the lease lifecycle unaddressed.

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% with five required parameters, so the description must compensate and it largely does not. Only 'token' loosely maps to fencing_token via the 'holder, token and expiry check' phrase; file_path, decision_key, decision_value, and rationale are left entirely to their bare schema titles.

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 specific verb+resource ('Record a decision') with an explicit precondition ('only while this agent holds the current lease'), which conceptually separates it from the sibling memkernel_append_decision. However, it never names the unfenced sibling or states the contrast explicitly, so the differentiation is inferential rather than stated.

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 precondition 'only while this agent holds the current lease' tells the agent when this tool is applicable, which is meaningful usage context. But it gives no guidance on the alternative (memkernel_append_decision) or what to do when no lease is held, leaving the routing decision to inference.

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