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

No annotations are provided, so the description carries the burden of behavioral disclosure. It indicates a read-only 'List' operation, which is a positive signal. However, it does not disclose any additional behavioral traits such as permission requirements, output format, or that it does not modify anything. The description adds minimal context beyond the obvious.

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, well-structured sentence. It is front-loaded with the action 'List' and immediately specifies the resource and scope. There is no wasted text.

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 simple one-parameter tool with no output schema, the description provides adequate context: it names the resource and gives a parenthetical clarification of what the access rules are. However, it does not mention output format or any side effects, but given the simplicity, it is nearly complete. Missing details like explicit return structure would push it lower.

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 0% and the slug parameter has no description. The description adds semantic meaning by implying that slug identifies the space whose rules are listed ('a space's fine-grained access rules'). However, this is indirect rather than explicitly stating 'slug is the space slug.' The description partially compensates for the schema gap but not fully.

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 clearly states a specific verb and resource: 'List a space's fine-grained access rules.' It also clarifies the rules are about member/manager status, which distinguishes it from unrelated list tools. The purpose is not a tautology and directly reflects the tool's function.

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 description implies usage context: you use this tool to list access rules for a space. However, it does not explicitly mention when to use this versus alternatives (e.g., brainkb_add_access_rule, brainkb_remove_access_rule), nor does it provide exclusions or prerequisites. The guidance is only implied.

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