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

With no annotations, the description carries the full burden. It does disclose real behavioral facts: this is a replacement (not an append), and the doctrine is 'read at the start of every turn,' which tells the agent when the change takes effect. However, it says nothing about authorization despite the required ownerKey, nothing about reversibility of the overwritten doctrine, and nothing about failure behavior.

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?

Three short sentences, front-loaded with the verb and resource. Each sentence earns its place: purpose, what the doctrine controls, authoring guidance, and a length constraint that is directly actionable for a content-generating agent.

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 two-parameter mutation tool with no output schema, the description covers the creative task well and explains the artifact's role in the turn loop. The gap is ownerKey semantics and any indication of what a successful or failed call returns, though the tool's simplicity limits the damage.

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%, so the description must compensate. It explains the content of the 'doctrine' parameter (personality and long-term strategy) and restates the length limit already encoded as maxLength 1000, but the second required parameter, ownerKey, is never mentioned or explained, leaving half the parameters undocumented.

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 and resource ('Replace the general's doctrine') and goes further by explaining what the doctrine is and how it functions in the game loop ('its personality and long-term strategy, read at the start of every turn'). No sibling does anything comparable, so differentiation is implicit 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?

'Keep what works, fix what lost' implies the situation in which a rewrite is warranted (after a losing turn), but there is no explicit when-to-use, no when-not-to-use, and no named alternative among the sibling tools. Usage is inferable but not spelled out.

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