Toggle fullscreen

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the toggle effect, but does not say whether an unfocused window fails, whether this requires a specific display, whether the change is persistent, or what the response is—significant gaps for a state-changing window operation.

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 front-loaded sentence with zero waste. It is appropriately sized, though the brevity contributes to the under-specification noted in other dimensions.

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 two-parameter, state-changing tool with no annotations and no output schema, the description is too thin: it omits the 'on' semantics, the display-id requirement, and the relationship to the 'resize' sibling, leaving the agent with real gaps before calling it.

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 only 50%: the 'id' parameter has a schema description, but 'on' has no description, only a default of true. The description adds no meaning—it never mentions the ability to force a state via 'on' or when 'id' is needed—so it fails to compensate for the gap.

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 gives a clear verb-plus-resource: 'Makes the focused window fullscreen (or restores it).' This lets an agent tell it apart from arbitrary resizing, but it does not name the sibling alternative 'resize' or otherwise explicitly distinguish the two.

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 parenthetical '(or restores it)' implies toggle behavior, and the 'focused window' wording implies the entry condition. However, there is no explicit guidance on when to use this versus 'resize', no statement of prerequisites such as a window needing focus, and no mention of what happens when no window is focused.

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