select

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing about behavior — not whether selection replaces or adds, what happens on failure, or how the four parameters interact. 'drop-down selection' is a label, not a behavioral statement.

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?

It is short, but this is under-specification rather than conciseness; the single fragment cannot earn its place because it conveys essentially no information.

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 four-parameter tool with no annotations, no output schema, and a same-domain sibling (select_option) that appears to do the same thing, this description is entirely inadequate to support correct invocation or disambiguation.

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?

Four parameters exist with 0% schema description coverage, and the description explains none of them. The mutual exclusivity of text/index/value versus the required selector is completely undocumented, leaving the agent to guess how to form a valid call.

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 'drop-down selection' only gestures at the action and resource without a clear verb, and it does nothing to distinguish this tool from the sibling select_option, which appears to overlap entirely. An agent cannot tell which of the two to invoke from this text.

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?

There is no guidance on when to use this tool versus select_option, checkbox, set_checked, or toggle_checkbox. No prerequisites or context are offered.

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