show_popup

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

With no annotations, the description must carry behavioral disclosure. It usefully describes the transient native window, top-right placement, glassy card, and auto-dismiss behavior, but omits details like whether multiple popups stack, whether focus is stolen, and any macOS permission or notification-center requirements.

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 tight sentences: the first front-loads the action and visual behavior, and the second gives usage guidance. There is no redundant restatement of schema fields or filler.

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 six-parameter display-only tool with full schema coverage and no output schema, the description covers purpose and usage well enough to invoke correctly. It could be more complete by naming dismissal/stacking behavior or pointing to dismiss_all_popups, but those are minor gaps.

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 the schema already defines title, level, screen, source, message, and duration. The description adds no parameter-level detail beyond the implicit auto-dismiss duration and screen targeting; baseline 3 is appropriate.

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 verb ('Show') and resource ('notification popup'), including platform and rendering context. It is clearly distinct from siblings like dismiss_all_popups and list_screens, though it does not explicitly differentiate itself from show_docs.

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 second sentence gives concrete use cases and a clear trigger: alerting Wael of important information such as task completion, deploy completion, or errors. It stops short of stating when not to use this tool or directing long-form content to show_docs.

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