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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the agent knows this mutates but is safe and repeatable. The description adds semantic context about what drawers_enabled actually does (stores raw tool output alongside summaries), which is genuine value beyond the annotations, but says nothing about permissions or side effects of toggling.

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?

Two short sentences with zero filler; the primary verb pair is front-loaded and the supported-setting detail follows immediately. Nothing needs to be cut.

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, but the tool is small and low-risk, and the schema fully documents the three parameters including the enum and conditional requirements. The description covers what the tool does and the sole supported setting, leaving only minor gaps such as return shape for 'get' and whether more settings are planned.

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%, including the get/set enum and the note that value/setting are required only for 'set', so the schema carries the parameter burden and the baseline is 3. The description reinforces the single valid setting name but adds no syntax or format detail beyond the schema.

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 pair (view/toggle) and resource (brain settings) and names the one setting currently supported, with a parenthetical explaining what it does. It does not explicitly distinguish itself from adjacent siblings like brain_update or brain_admin, but the resource is clear enough that an agent can pick it without opening other schemas.

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?

Usage is implied by the verb pair 'view and toggle' and the note that only drawers_enabled is currently supported, but there is no explicit when-to-use guidance or pointer to alternatives such as brain_update or brain_admin. An agent can infer intent but is not routed.

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