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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the tool is gated to Admin/SuperAdmin, and the result includes built-in system reservations (metadata/provenance graphs) that nobody can bind. It stops short of describing return shape, ordering, or what happens for an unauthorized caller, but the auth and immutable-built-in disclosure is substantive.

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 leads with the action ('List reserved named graphs'), then uses a compact appositive to define the concept and a final clause to flag the built-in reservations. No sentence is wasted.

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 zero-parameter list tool with no output schema and no annotations, the description supplies the conceptual grounding (what 'reserved' means, who is allowed) and the special case of built-in system graphs. The main gap is that the shape of the returned list is not described, but an agent has enough to invoke it 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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly implies no filtering input is required.

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 states a specific verb and resource ('List reserved named graphs') and goes further by defining what a reservation means (graph IRIs or prefix IRIs that only admins, or a space's managers/editors, may register or bind). This implicitly separates it from brainkb_list_registered_graphs, but it never names that sibling explicitly, so it falls short of a 5.

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?

The '(Admin/SuperAdmin)' prefix signals the calling context and the text explains that reservations gate who may register or bind a graph, which implies when an agent would consult this list. However, it never states when to use this versus brainkb_list_registered_graphs or brainkb_unreserve_graph, leaving the choice to inference.

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