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

All annotations are false, so the description carries the full burden of behavioral disclosure. It does mention the team_sleep lifecycle and its admin requirement, but it does not explain the side effects or risks of link, promote, lint, or rebuild_index, whether operations are reversible, or what success/failure looks like. This is a significant gap for a mutating admin 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?

The description is compact and front-loaded: scope, action list, then team_sleep-specific instructions. Each sentence contributes useful information without filler. The team_sleep sentence is longer than the others, but that complexity is inherent to the subcommand structure.

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?

This is an eight-parameter administrative tool with no output schema and no informative annotations, yet the description only fully explains the team_sleep branch. The semantics, side effects, and result behavior for link, promote, lint, and rebuild_index are left almost entirely to parameter names and schema descriptions. That is insufficient for safe and correct use of the non-team_sleep actions.

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 100%, and every parameter already has a meaningful description and enum where appropriate. The description adds useful cross-parameter context for team_sleep (sub_action values, optional timezone, default UTC, 3 AM behavior), but much of that is also present in the schema, so the value added is incremental rather than transformative.

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 identifies an administrative resource ('Brain admin operations') and enumerates five specific executable actions: lint, link, promote, rebuild_index, team_sleep. This goes well beyond a tautology and tells an agent what the tool can do, though it does not explicitly distinguish the tool from siblings like brain_lint or brain_settings.

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 provides explicit usage guidance for the team_sleep subcommand: which sub_action values to pass, that timezone is optional, and that a team admin role is required. However, it gives no guidance on when to prefer brain_admin over the dedicated sibling tools, nor when individual actions like link vs promote vs rebuild_index should be chosen.

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