stop_virtual_display

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

Annotations already mark it destructive and idempotent. The description adds value by explicitly stating it terminates apps launched on the display, and discloses the return JSON shape. This goes beyond annotation basics.

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 brief, front-loaded with the main action, and clearly separates Args and Returns. Every sentence is useful with no fluff.

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 tool is simple, and the description covers its scope, side effects, and return format. It doesn't explain edge cases like missing displays, but given the structure and annotations, it's adequately complete.

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 schema describes 'display' as 'Xvfb display number'. The description repeats this as 'display number' without additional detail. Since the top-level schema coverage is 0%, the description partially compensates but doesn't add meaningful semantics 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 stops an Xvfb virtual display and terminates its apps. The verb 'stop' and resource 'Xvfb virtual display' differentiate it from siblings like create_virtual_display or launch_on_virtual_display.

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?

Usage is implied by the purpose: it's for stopping a display. However, there is no explicit guidance on when to use this vs alternatives, or when not to use it. The context from sibling names helps but the description doesn't directly address selection.

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