app_select

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

Describes the action of picking an option but does not cover error handling, preconditions like dropdown state, or behavior when no match is found. With no annotations, the description carries the full burden but falls short of full transparency.

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 sentences with no extraneous words, front-loading the primary action and quickly covering the selection criteria.

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 straightforward selection tool, the description covers the key aspects: how to locate the select and how to specify the option. The lack of output schema is not a problem as no return values need explanation.

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 description adds context by explaining the two-step process and the mutual exclusivity of option parameters, but each parameter's details are already provided in the schema, so additional value is limited.

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 tool selects an option from a native <select> dropdown using specific identifiers, distinguishing it from sibling tools like app_click or app_read.

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?

Provides explicit guidance on locating the <select> element and choosing an option via exactly one of text, value, or index. However, it lacks explicit exclusions or comparison to sibling tools.

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