Show or hide the menu bar

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

Annotation only says readOnlyHint=false; the description goes well beyond that by naming the concrete element (#toolbar-menubar), disclosing its default autohide="true" state, and explaining that true clears autohide while false restores it — a reversible, mechanism-level account of the mutation. It stops short of saying whether the change persists across restarts or where it is stored.

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?

Three short sentences, zero redundancy: purpose first, then the measured DOM fact, then the effect of each flag value. Nothing could be removed without losing information.

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 single-boolean toggle with a fully-documented schema, minimal annotations and no output schema, the description covers everything needed to call it correctly. Only the persistence/return behavior is left unstated, a minor gap.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning the schema does not: the parameter works by clearing the autohide attribute rather than merely 'pinning' the bar. That mechanistic detail helps the agent predict the outcome of each value.

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 and resource ('Show or hide the classic menu bar'), with the parenthetical File/Edit/View clarifying which menu bar. The qualifier 'classic' implicitly separates it from browser_set_toolbar_visibility and browser_set_main_menu, though no sibling is named explicitly.

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 explains the semantics of each flag state and the default autohide condition, which implies usage. It never states when to reach for this versus browser_set_toolbar_visibility or browser_set_main_menu, and gives no prerequisites or exclusions.

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