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

With no annotations, the description carries the full burden and delivers: it discloses the exact authorization checks (owner/editor membership including inherited parent roles, space write access rule, Admin/SuperAdmin), the meaning of can_ingest=false, and what unmapped_graphs represents. This is unusually rich behavioral context for a read tool.

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?

Front-loads the core purpose ('Spaces the caller can ingest into') and keeps the field explanations tight. The dense em-dash clause about access checks is information-rich but slightly heavy, keeping it just under fully optimal.

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?

There is no output schema, yet the description describes the returned shape (graphs with descriptions, parent_slug for subspaces, can_ingest, unmapped_graphs). An agent has everything needed to call and interpret the result.

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 the schema baseline is 4. There is nothing to add; the description instead spends its budget on return-field semantics, which is the correct allocation.

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 a specific verb+resource: spaces the caller can ingest into, and explains the access basis that defines 'writable'. It explicitly differentiates from a sibling by name ('Use this, not brainkb_list_registered_graphs'), so an agent can distinguish it without opening a schema.

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?

Provides explicit when-to-use ('to choose where to ingest') and names one alternative to avoid (brainkb_list_registered_graphs). It does not address the closely related brainkb_list_spaces sibling, leaving a minor routing gap, so not a full 5.

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