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

There are no annotations, so the description carries the full burden, but with zero parameters this is plainly a static reference fetch. The description does disclose the content structure, which is the key behavioral fact, yet it says nothing about size, caching/staleness, or the format of what is returned. 'CLEAR' is used without definition.

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?

A single front-loaded sentence that names the resource first and then enumerates its parts. The parenthetical gloss on signatures is worth its space; nothing is padded, though the enumerated list is dense and could be skimmed past.

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?

With no output schema, the description must convey the shape of the return value, and it does so by listing the sections (verbs, patterns, glossary, units, connectors). An agent knows what it will get, though it cannot tell whether results are versioned or how large the payload is.

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 tool takes no parameters, so the baseline applies. The description does not need to explain inputs, and it usefully clarifies that signatures mean 'the arguments each takes', which helps an agent interpret the returned data.

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 names a concrete resource (the CLEAR vocabulary used by the Gate) and enumerates its contents — approved verbs with signatures, question patterns, glossary, units, connectors. That is specific enough to distinguish it from siblings like 'check', 'commands' or 'schema', though it describes the payload rather than stating the action (e.g. 'returns' or 'lists').

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?

Use is only implied: an agent can infer it should call this to learn approved verbs and their argument signatures before phrasing a request. There is no explicit when-to-use or when-not-to-use statement, and no differentiation from potentially overlapping siblings such as 'schema' or 'commands'.

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