field_dropdown_state

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

With no annotations, the description must carry behavioral context, but it only names the return values. It does not disclose that the call may wait (timeout param), what happens when the dropdown is closed, or whether invoking it changes state. A read query's safety is only implied, never stated.

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?

One sentence with no filler, and the output focus is front-loaded. However, it is under-specified rather than a model of concision, so it earns only an average score.

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?

The description gives the tool's high-level result but no parameter semantics, usage context, or expected return structure. With four parameters and no output schema or annotations, this is not enough for reliable 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?

Schema description coverage is 0%, and the description does not define field_name, search_by_title, session_id, or timeout. 'search_by_title' in particular is ambiguous and needs explanation. This forces the agent to guess the meaning of most arguments.

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?

States a specific read operation ('Return whether...') and identifies the exact output: dropdown open state and visible choice items. It is distinguishable from siblings like field_dropdown_close and field_dropdown_items by combining state with visible items, though it doesn't explicitly draw the contrast.

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 on when to call this versus field_dropdown_items or field_dropdown_close, nor any criteria such as needing current state before interacting. The absence of any usage condition makes this a no-guidance dimension.

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