ui_fullscreen

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

With no annotations, the description carries the full burden and does disclose the critical trait: STATE_MUTATING, toggling fullscreen. 'Toggles' also hints that a repeated call reverts the state. It stops short of stating whether a chart/tab must be active or focused, and 'LIMITATIONS: None' is uninformative filler.

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?

Front-loaded with the action, then labeled WHEN TO USE and SIDE EFFECTS sections. Very compact; only the 'LIMITATIONS: None' line fails to earn its place.

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-parameter, no-output-schema toggle, the description covers what it does, when to call it, and that it mutates state — enough to invoke correctly. Minor gap: no confirmation of what state is left in or any precondition about an open chart.

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?

Zero parameters, so there is no schema semantics to compensate for; the baseline of 4 applies. Nothing about arguments is needed or missing.

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: 'Toggle TradingView window chart fullscreen mode.' No sibling tool in the list performs fullscreen control, so the agent can identify it immediately from the name plus description.

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?

'WHEN TO USE' gives concrete triggers: expanding the chart canvas for clean screenshot captures or presentation view. Clear context, but no explicit when-not or alternative (e.g. capture_screenshot without fullscreen) is offered.

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