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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. However, the description adds no behavioral context beyond the ambiguous words 'closed' and 'frozen', which do not clarify side effects, pagination, authentication, or any operational constraints. It contributes nothing beyond what annotations already state.

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 it is under-specified rather than concise. It does not front-load key operating details or enumerate the operations. The sentence adds little value and reads more like a placeholder or tautology than a structured explanation.

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 complex tool with six operations, nested payload variations, no output schema, and a large sibling set. The description is completely inadequate: it neither explains the family of operations nor guides the agent toward correct usage. Given the tool's complexity, the description must do far more to be complete.

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 for missing parameter explanations. It provides zero information about the operation or payload fields, leaving all semantic burden to the oneOf/enum schema. This is a significant gap for a tool with two top-level parameters and nested payloads.

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?

Description only says 'Use the closed knowledge read capability family from the frozen Brain Scanner policy.' This restates the tool's name without identifying a specific verb or resource, and does not distinguish it from sibling tools like knowledge_write, graph_read, or context_read. It fails to mention the six distinct operations (list_reports, get_report, etc.) that define the tool's actual purpose.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that this is a family of read operations, does not differentiate between the operations, and gives no selection criteria. Agents are left to parse the schema's oneOf construct without any hint about context or exclusions.

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