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

With no annotations provided, the description carries the full burden. It discloses admin-only auth, group-wide effect (EVERY member), prerequisite (create group first), and capability restrictions. While it does not mention reversibility or return value, the core behavioral traits are sufficiently covered.

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 concise and front-loaded with the core purpose. It uses an em-dash for the example and includes necessary exclusions and workflow without redundancy. Every sentence contributes value.

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 only two simple parameters and no output schema, the description covers purpose, authorization, prerequisites, and valid inputs. It is complete enough for an agent to select and invoke correctly without additional context.

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%, but the description fully compensates. It defines 'capability' as one of the listed grantable capabilities and clarifies that 'role' is a group created via brainkb_create_role. Examples provide concrete expected values, making the parameters unambiguous despite lack of enums.

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 the action 'Grant a capability to a whole role/group' and its effect 'so EVERY member gets it'. It provides concrete examples (e.g., 'uk_collaborator' with 'ingest') and distinguishes from sibling tools like brainkb_grant_capability by emphasizing the role/group scope and from brainkb_revoke_role_capability by the grant verb.

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?

It specifies the admin-only requirement, lists grantable capabilities explicitly (create_private_space, create_team_space, etc.) and exclusions (NOT 'grant'/'sparql_admin'). It also gives a workflow: create the group first with brainkb_create_role, then assign users with brainkb_assign_role, providing clear when-to-use context and alternatives.

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