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

Annotations already convey readOnlyHint=false and destructiveHint=false; the description adds no behavioral detail about what happens on write, what 'closed' means in practice, or how idempotency is handled. 'Frozen Brain Scanner policy' is too vague to inform an agent's expectations.

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 short, but the brevity is under-specification rather than conciseness. It front-loads a policy directive that carries no operational meaning for an 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?

This is a highly complex tool with nine distinct write operations, nested schemas, and no output schema. The description leaves out the purpose, operation selection, semantics of payload fields, and relationship to sibling tools, making it inadequate for correct invocation.

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?

The description provides zero parameter context while the schema has 0% description coverage. The schema's oneOf with nine operation variants and nested payloads requires explanation of how to select an operation and what each payload means; the description does not compensate at all.

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 only says 'use the closed knowledge write capability family,' which is essentially a restatement of the tool's name and a policy label. It never states what knowledge writes actually do—create/update reports, findings, reviews, and investigations—and it does not differentiate from sibling tools like knowledge_read or the individual create_report/update_report tools.

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 on when to invoke this family versus alternatives such as create_report, save_investigation, or knowledge_read. The phrase 'from the frozen Brain Scanner policy' is opaque and gives no selection criteria, prerequisites, or when-not-to-use information.

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