set_checked

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

Description adds key behavioral detail: radios cannot be unchecked directly, beyond the idempotent and non-destructive annotations. No contradictions.

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?

Two efficient sentences with no fluff; directly states purpose and special case for radios.

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?

Description gives core behavior but omits parameter contexts for target/frameId. With no output schema, more detail on return values would help. Adequate for simple tool.

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?

Only 25% schema coverage; description does not explain 'target' or 'frameId' parameters, though it clarifies the role of 'checked'. Schema covers 'returnSnapshot'.

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?

Description clearly states it sets checkbox state or selects radio element, with specific behavior for each. Distinguishes from siblings like click or select_option.

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?

Description makes clear the tool is for checkboxes and radios, but does not explicitly contrast with alternatives or mention when not to use it.

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