点击弹窗按钮

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

Annotations only provide readOnlyHint: false, so the description carries the behavioral burden. It discloses that the tool automatically finds visible .ant-modal, targets footer or confirm areas, and performs a real click. It also implicitly includes waiting via the timeout parameter. This adds useful behavioral detail without contradicting annotations.

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 wasted words. The core purpose and mechanism are front-loaded, and examples are concise. It is appropriately sized for the tool's simplicity.

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?

Given the tool's narrow scope, an output schema, and full parameter documentation, the description covers the essential behavior: finding a visible modal and clicking a matching button. It could mention behavior on multiple visible modals or failure cases, but these are minor and not required for a correct call.

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 100%, so all five parameters are documented in the schema. The description adds examples of button text ('确定', '取消') but does not explain parameter semantics beyond the schema. Baseline 3 applies because the schema does the heavy lifting.

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 it clicks a button in a visible AntD modal, naming specific modal types (Modal.confirm / Modal) and giving examples of button texts. It differentiates from generic element_click and other antd tools by scoping to modal-specific interactions.

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 provides clear context for when to use it: when a visible AntD modal contains a button to click. It implies this is the dedicated tool for modal buttons, but it does not explicitly name alternatives or state when not to use it. Thus it has clear context without exclusions.

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