fcp_click_button

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

Annotations already declare destructiveHint=true, so the safety warning is present. The description adds only the target-window context and does not disclose prerequisites such as a dialog needing to be open, potential irreversible consequences of clicking, or any confirmation behavior.

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 a single, front-loaded sentence with no wasted words. It is appropriately sized for a simple one-parameter UI action.

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 simple one-parameter action with a fully described schema and destructive annotation, the core is present. However, it lacks differentiation from other UI tools and omits safe-use context that would help an agent invoke it correctly in complex automation flows.

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 coverage is 100% and the single "label" parameter is already documented with examples like "Next", "Cancel", "Import", and "OK". The description adds no additional meaning beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb ("Click") and resource ("button") for Final Cut Pro, with target context of the open dialog or front window. It is clear but does not distinguish this action from sibling UI tools such as fcp_menu_click or fcp_press_keys.

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 parenthetical "(or front window)" implies the tool is for interacting with an open dialog or active window, but there is no explicit when-to-use guidance, no when-not guidance, and no routing to alternative UI-automation siblings.

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