open_in_app

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

Annotations are minimal (readOnlyHint, destructiveHint, openWorldHint). The description adds critical behavior: macOS only, fallback to browser preview, filePath autosaving and live re-render, and the distinction between ephemeral and persistent modes.

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?

Five sentences, front-loaded with the main action and platform. Every sentence adds essential information without redundancy 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?

No output schema, but the description explains the two modes and fallback. It covers platform restriction and file persistence. Could mention installation requirement more explicitly, but 'preferred path when app is installed' implies it.

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% with descriptions. The description adds value by explaining that filePath opens the exact file for live editing (source of truth) and that dgmo is the markup. This enriches the basic schema definitions.

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 specifies the verb 'open', the resource 'DGMO diagram', and the platform 'macOS only'. It distinguishes from sibling tools like 'preview_diagram' by noting fallback behavior and file handling.

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 guidance on when to use filePath (for saved files with live editing) vs omit (ephemeral diagram). It implicitly contrasts with preview_diagram as fallback, but does not explicitly list when not to use.

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