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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'read capability family' is consistent with those. It adds a little API-design context with 'closed' and 'frozen Brain Scanner policy', but it does not disclose operation-specific effects, auth needs, return shapes, or error behavior. This is acceptable given the annotations, but the description itself adds only marginal behavioral context.

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 this is under-specification rather than effective conciseness. Phrases like 'closed project read capability family' and 'frozen Brain Scanner policy' are opaque jargon that do not earn their place. A concise description should pack useful information into few words; this one packs almost none.

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 oneOf dispatcher with nine operations, nested payload objects, no output schema, and zero schema description coverage. The description does not enumerate the operations, explain how to construct a valid operation/payload pair, or describe expected return values. Despite the annotations covering safety, the definition is far too incomplete for an agent to use correctly.

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?

With 0% schema description coverage, the description needed to explain that `operation` selects one of the nine behavior branches and that `payload` must match the selected branch. It does neither — the oneOf/const structure in the schema is the only source of parameter meaning. The description contributes zero parameter semantics.

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 project read capability family from the frozen Brain Scanner policy' — this essentially restates the tool name project_read without naming any concrete action, output, or sub-operation. It doesn't tell the agent what actually happens when the tool is invoked, and the nine operation constants are buried in the schema rather than surfaced in the description. This is closer to a tautology than a specific verb+resource statement.

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 this tool versus sibling read tools like context_read, graph_read, scope_read, or project_write. It neither names alternatives nor states exclusions, and 'Use ...' is an invocation directive rather than usage guidance. The description provides no decision-relevant context for tool selection.

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