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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is clear. The description adds no behavioral detail beyond broad domains; it does not explain the claim booleans (is_spawn, is_write, etc.), evaluation semantics, or what an explanation returns.

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 a single front-loaded sentence with no filler. It is concise and easy to parse, though its brevity contributes to under-specification rather than excess length.

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 tool with seven optional parameters, no output schema, and non-obvious claim-evaluation fields, the description is too thin. It omits how concept, tool_name, args_hash, and the boolean claims combine, and gives no expectations about the returned explanation.

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 100%, so all seven parameters are documented in the input schema. The description adds no parameter meaning and does not tie concept, tool_name, args_hash, or the claim fields to the explanation purpose. Baseline 3 is appropriate when the schema carries parameter documentation.

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 the verb 'Explain' and three domains (architectural invariants, memory schemas, routing logic), so the general purpose is inferable. However, it does not say what inputs trigger each mode or how it differs from gnosis.status, leaving the scope broad.

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 when-to-use, when-not-to-use, prerequisite, or alternative-tool guidance is provided. The agent must infer that this is for internal conceptual explanation rather than memory search, session recall, or other sibling operations.

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