classic_mac_get_front_window

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

No annotations are provided, so the description must disclose behavioral traits. It states 'Get detailed info' implying read-only, but does not explicitly confirm no side effects, required permissions, or potential errors. The phrase 'Requires AgentBridge' is a prerequisite, not a behavioral trait. Some transparency is present but incomplete.

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 sentence, front-loading the purpose and key outputs. Every word contributes meaning; no redundant or filler content.

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 lists the specific information returned (title, app, bounds), which is sufficient for a simple query tool. It does not describe the return format (e.g., JSON), but given the simplicity and no output schema, this is acceptable. The sibling context shows many similar tools, but this one is self-contained.

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 input schema covers the one parameter ('target') with description 'Target ID or alias. Optional if only one target is configured.' The tool description does not mention this parameter or add any extra meaning. Since schema description coverage is 100%, baseline is 3, and the description provides no additional value here.

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 gets detailed info about the frontmost window, listing title, app, and bounds. It uses a specific verb ('Get') and resource ('front window'), distinguishing it from sibling tools like classic_mac_list_windows (which lists all windows) and classic_mac_get_menu_items.

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 does not explicitly state when to use this tool versus alternatives. It mentions 'Requires AgentBridge' but provides no guidance on when to use this tool over classic_mac_list_windows (e.g., for the front window vs. all windows). Usage context is only implied.

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