fx_toggle

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'set checkbox/radio state' without explaining whether it toggles or sets an absolute value, how it selects the target (via ref or selector), or any side effects. This is insufficient for an agent to predict behavior.

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?

The description is extremely concise (one sentence), but it is under-specified rather than efficiently concise. It lacks any structured guidance or additional context that would make the brevity helpful. The absence of detail makes it an inadequate representation of the tool's purpose.

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?

Given the tool has three parameters, no annotations, and no output schema, the description is severely incomplete. An agent cannot determine how to construct a valid call or what to expect as a result. The description fails to provide essential context for correct invocation.

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 schema has three parameters with only 'on' having a description ('default true'), giving 33% coverage. The description does not explain the roles of 'ref' or 'selector' or how 'on' relates to the state. With such low schema coverage, the description must compensate, but it adds no parameter-level meaning.

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 clearly states the action ('set') and the resource ('checkbox/radio state'). It is specific and understandable, though it does not explicitly differentiate from sibling tools like fx_click or fx_select. The verb-resource combination is sufficient for a basic understanding.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention contexts such as 'use this to change the checked state' or differentiate from clicking or selecting options. Without any sibling comparison or usage conditions, an agent cannot determine when this is the right tool.

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