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

The annotations already indicate idempotent, non-read-only, and non-destructive behavior, so the description has a lower bar to meet, but it still adds almost nothing. It does not disclose that this is a multi-operation dispatcher, that payloads vary by operation, that expectedVersion enables optimistic concurrency, or what side effects occur. 'Closed' and 'frozen policy' hint at restrictions but do not explain 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?

The description is one short sentence, but this is under-specification, not conciseness. For a tool with nine operation variants and nested payload objects, the single sentence provides no useful structure or front-loaded information.

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 the complex oneOf schema, 0% parameter coverage, no output schema, and a large sibling list, this description is severely incomplete. An agent cannot determine how to pick an operation, construct a valid payload, interpret the result, or understand policy constraints.

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 carries the full burden of explaining parameters, but it explains none. It does not clarify what operation and payload mean, how to choose an operation, or what fields are required for each variant. The rich oneOf structure is left entirely for the agent to infer.

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 restates the tool name ('context write capability family') and adds only vague policy context ('frozen Brain Scanner policy'). It does not state a concrete verb-resource action, such as 'executes context-graph mutations' or 'dispatches context write operations', nor does it distinguish itself from sibling operation-specific tools like archive_context_note or update_context_note.

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 guidance about when to use context_write versus the many sibling tools, some of which carry the same operation names as the enum values in the schema. The description merely says 'use' this family; it never explains when it is preferred, when it is not, or what alternatives exist.

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