projector_fullscreen

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

Annotations already declare this is a non-readOnly but non-destructive, closed-world action, and the description usefully adds what actually changes on screen (status bar and navigation hidden). However, it omits whether the state persists, whether there is any way to exit immersive mode, and whether an active projector session is required — important for a mutation with no undo path documented.

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?

A single sentence that front-loads the action and then the visible effect. No filler, no redundancy with the name or title.

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 zero-param state-changing command this is close to sufficient, but it leaves out how to reverse the immersive mode and how it relates to the various other projector_* and toggle_fullscreen siblings. There is no output schema, so nothing needs explaining about return values.

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?

The tool takes zero parameters and the schema confirms an empty object, so there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter hints are present.

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 ('Enable fullscreen immersive mode on the projector') plus the concrete effect (hides status bar and navigation). It is clear what it does, but it does not distinguish itself from the sibling toggle_fullscreen, which an agent could easily confuse this with.

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 'Enable' (a one-way activation, not a toggle), but the description never says when to prefer this over toggle_fullscreen or projector_setup, nor whether the projector must be set up/woken first. No alternatives or exclusions are named.

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