classic_mac_send_appleevent

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

With no annotations, the description must fully disclose behavioral traits. It only states the action without side effects, permissions, error handling, or state changes. Sending a generic Apple Event can alter application state and may require specific privileges, which are not mentioned.

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 extremely concise: two sentences with no redundant information. It front-loads the core action and includes key details (target, event, dependency) without waste, earning every sentence.

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 complexity of sending Apple Events and the lack of output schema or annotations, the description is incomplete. It omits success indicators, error handling, return behavior, and contextual constraints, leaving the agent inadequately informed for proper 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 100%, so baseline is 3. The description adds examples ('oapp') and clarifies target as app name/creator code, but mostly restates schema. It provides minimal extra semantic value beyond structured fields.

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 sends a generic Apple Event to an application, specifying the verb 'send' and resource 'Apple Event'. It provides example event types ('oapp'), but does not explicitly distinguish from sibling tools, though their names suggest different operations.

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 is given on when to use this tool versus alternatives like specific app control tools (e.g., classic_mac_launch_app). The description lacks indications of prerequisites beyond 'Requires AgentBridge' and does not mention situations where this tool should not be used.

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