activate

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

With no annotations, the description fully describes behavior: clicking, settling, and returning before/after URLs, summaries, network counts, hashes, and classification of effects. It covers all essential behavioral aspects for an agent.

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 two sentences, efficiently packing all key information: action, input, steps (click + settle), and output. No unnecessary words.

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?

Despite no output schema, the description lists all return components (URLs, summaries, etc.) and classification. The input schema is well-covered. The tool is distinct from its many siblings, and the description ensures an agent knows when and how to use 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?

Input schema has 100% coverage with descriptions. The description adds context by explaining that 'ref' or 'text' identifies the element to click, confirming their roles and usage. This goes beyond the schema.

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 specifies that 'activate' clicks an element (by ref or text), settles, and returns detailed output with classification. It distinguishes itself from simpler actions like 'click' or 'type' by being a higher-level probe with comprehensive return data.

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 description states it is a 'higher-level action probe', implying a comprehensive action. It does not explicitly state when to use versus alternatives, but the detailed output and classification hint at scenarios requiring full analysis. Slightly lacking in explicit exclusion guidance.

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