preview_diagram

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

Annotations give readOnlyHint=false and destructiveHint=false. The description adds behavioral context by stating it opens an HTML preview in the browser and supports theme toggling, but does not mention potential side effects like preventing concurrent operations or browser tab management.

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 two sentences, front-loading the core action and adding a concise usage hint. Every sentence provides value without redundancy.

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 tool's complexity (four parameters including nested array, optional fields) and no output schema, the description adequately covers the basic preview functionality but lacks details on browser interaction, error cases, or the `openWorldHint` implication.

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 parameters are well-documented in the schema. The description reinforces the color label rule and provides an example, but does not add significant new meaning beyond the schema.

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 renders DGMO diagrams and opens an HTML preview in the browser, including support for theme and source display. It differentiates from siblings like 'render_diagram' by explicitly mentioning the browser preview, but does not directly compare to related tools.

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 implies usage for previewing DGMO diagrams and references `get_language_reference` for syntax help, providing some guidance. However, it does not specify when to use alternatives like `render_diagram` or `validate_diagram`, nor does it indicate prerequisites or exclusions.

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